Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d001601f4ca74ca4eb3ab93312521842cc45df7a2bf21de8faf59f160e8dee8

Tx prefix hash: 01a02d38a6b0b447d536c9a5dc5734f2325623bf0dea72b0cc15a1407945005f
Tx public key: 255a9f13d1f3d49ce57fc74083b8f544a940dcb482ae5376b5e23a559f572b82
Timestamp: 1740925584 Timestamp [UCT]: 2025-03-02 14:26:24 Age [y:d:h:m:s]: 00:263:14:01:40
Block: 1230573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186127 RingCT/type: yes/0
Extra: 01255a9f13d1f3d49ce57fc74083b8f544a940dcb482ae5376b5e23a559f572b820211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b28e97b9a5731287f22f78c0c45dfa30dab5596fafb0181c81b1a17de20a2027 0.600000000000 1717472 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": 1230583, "vin": [ { "gen": { "height": 1230573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b28e97b9a5731287f22f78c0c45dfa30dab5596fafb0181c81b1a17de20a2027" } } ], "extra": [ 1, 37, 90, 159, 19, 209, 243, 212, 156, 229, 127, 199, 64, 131, 184, 245, 68, 169, 64, 220, 180, 130, 174, 83, 118, 181, 226, 58, 85, 159, 87, 43, 130, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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