Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e2fd4b772a4e5d92f175650729066887d6f24ec15f5eebac742c17791fc1d8f

Tx prefix hash: ba5e0cb516891123508d142fdd51cf464cfb88e012445063f07d08b6fa401311
Tx public key: 670f7e8694c7b66ce43fb5eb0984cb02657ca0d27a88ee3e1f908e900dcb49aa
Timestamp: 1758243107 Timestamp [UCT]: 2025-09-19 00:51:47 Age [y:d:h:m:s]: 00:051:23:34:48
Block: 1371502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37218 RingCT/type: yes/0
Extra: 01670f7e8694c7b66ce43fb5eb0984cb02657ca0d27a88ee3e1f908e900dcb49aa021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4949f0899ebbdcec61a4d25fb502489d4f88b174be302442f5f28b83b7f1e70e 0.600000000000 1859579 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": 1371512, "vin": [ { "gen": { "height": 1371502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4949f0899ebbdcec61a4d25fb502489d4f88b174be302442f5f28b83b7f1e70e" } } ], "extra": [ 1, 103, 15, 126, 134, 148, 199, 182, 108, 228, 63, 181, 235, 9, 132, 203, 2, 101, 124, 160, 210, 122, 136, 238, 62, 31, 144, 142, 144, 13, 203, 73, 170, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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