Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8445c4c19580c921d1222a970469610f18c2b6d19df5d877a7446432f0350f1a

Tx prefix hash: 34a7448bf1c718e16fd46e65c3f1e37a6969a219e6939128ad8f362936be4ed4
Tx public key: 8f1527a7f8d3929673054dcfde24e375fe2b6b76ce490290326d14bd2827c364
Timestamp: 1696571228 Timestamp [UCT]: 2023-10-06 05:47:08 Age [y:d:h:m:s]: 01:231:13:19:57
Block: 863520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426570 RingCT/type: yes/0
Extra: 018f1527a7f8d3929673054dcfde24e375fe2b6b76ce490290326d14bd2827c36402110000000775e3f0e9000000000000000000

1 output(s) for total of 0.844889305000 dcy

stealth address amount amount idx
00: 44f6a9b385021340c88e8a613c7a278dabc6611e60b6f50f008622252f900630 0.844889305000 1317978 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 863530, "vin": [ { "gen": { "height": 863520 } } ], "vout": [ { "amount": 844889305, "target": { "key": "44f6a9b385021340c88e8a613c7a278dabc6611e60b6f50f008622252f900630" } } ], "extra": [ 1, 143, 21, 39, 167, 248, 211, 146, 150, 115, 5, 77, 207, 222, 36, 227, 117, 254, 43, 107, 118, 206, 73, 2, 144, 50, 109, 20, 189, 40, 39, 195, 100, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8