Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b65870b83a83440c865d2d03c912a9dc4d67dcce1e6d70d50baf6e1545c24fe

Tx prefix hash: a2da32a2449664140c2a1e0d74a98bef48cb06f3b72a49683fec6383e9624d47
Tx public key: c9f3d1cbfb126746e00cb9e8d6f22be70659b25968fa2f4433b9ae57fa8591b5
Timestamp: 1712256891 Timestamp [UCT]: 2024-04-04 18:54:51 Age [y:d:h:m:s]: 01:225:12:00:16
Block: 993348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419858 RingCT/type: yes/0
Extra: 01c9f3d1cbfb126746e00cb9e8d6f22be70659b25968fa2f4433b9ae57fa8591b502110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88fd759ed30d8b07d5d31e85bdd79dc123bf7c7605dc688b44ee23f28d090b6e 0.600000000000 1453734 of 15

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": 993358, "vin": [ { "gen": { "height": 993348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88fd759ed30d8b07d5d31e85bdd79dc123bf7c7605dc688b44ee23f28d090b6e" } } ], "extra": [ 1, 201, 243, 209, 203, 251, 18, 103, 70, 224, 12, 185, 232, 214, 242, 43, 231, 6, 89, 178, 89, 104, 250, 47, 68, 51, 185, 174, 87, 250, 133, 145, 181, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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