Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26dc3886287330c0033d58b80790a811e3c901736c6d0f5a74c5c172a38b7060

Tx prefix hash: 33839f9cdb475f4630d360d47b5acdcaeddadf87c1100200e5ff0ba0f936ba57
Tx public key: b9395b5bc5d983e08f285fcbb447ec4a9e96a6707f2f8c31f381a67dcee6862a
Timestamp: 1751848930 Timestamp [UCT]: 2025-07-07 00:42:10 Age [y:d:h:m:s]: 00:131:00:33:55
Block: 1320269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92056 RingCT/type: yes/0
Extra: 01b9395b5bc5d983e08f285fcbb447ec4a9e96a6707f2f8c31f381a67dcee6862a02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c68d22167ea055fb869d21ca9d1249f060b8953c201e1de04237f077a2b288d4 0.600000000000 1807966 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": 1320279, "vin": [ { "gen": { "height": 1320269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c68d22167ea055fb869d21ca9d1249f060b8953c201e1de04237f077a2b288d4" } } ], "extra": [ 1, 185, 57, 91, 91, 197, 217, 131, 224, 143, 40, 95, 203, 180, 71, 236, 74, 158, 150, 166, 112, 127, 47, 140, 49, 243, 129, 166, 125, 206, 230, 134, 42, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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