Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 503170212056a333d0c37733bf67e957c2c2a9fb52693f139fe5e03c6f1004c7

Tx prefix hash: b878b65fe8ac57afe7d2d8870af3faa70e733da7caa2b01cefeae69aa4c65a3b
Tx public key: ef12eb58ae0e9de8a53f1bb73cf1dc1e9820b1ed751f0ad27df749f4e5bd5e1f
Timestamp: 1694137861 Timestamp [UCT]: 2023-09-08 01:51:01 Age [y:d:h:m:s]: 01:222:05:57:02
Block: 843329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419948 RingCT/type: yes/0
Extra: 01ef12eb58ae0e9de8a53f1bb73cf1dc1e9820b1ed751f0ad27df749f4e5bd5e1f021100000006faf35c9c000000000000000000

1 output(s) for total of 0.985600708000 dcy

stealth address amount amount idx
00: a3dec84ebcf125b757ba3e25b99c93ba916cefb6643c769164a57cd088853963 0.985600708000 1296549 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": 843339, "vin": [ { "gen": { "height": 843329 } } ], "vout": [ { "amount": 985600708, "target": { "key": "a3dec84ebcf125b757ba3e25b99c93ba916cefb6643c769164a57cd088853963" } } ], "extra": [ 1, 239, 18, 235, 88, 174, 14, 157, 232, 165, 63, 27, 183, 60, 241, 220, 30, 152, 32, 177, 237, 117, 31, 10, 210, 125, 247, 73, 244, 229, 189, 94, 31, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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