Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 369e886cf5de7d115b37b8abdea3f40a5938618850e3504b147fe0666332f85a

Tx prefix hash: 0e2e9261eee5dfe5fdf8a77fac324fc918b68fdd2091c693115df3fe974312e3
Tx public key: b87839555bd2a3c6b5582823580e697d7dd08f9228f9c4a4fa1e7c9fb1c31a38
Timestamp: 1727472216 Timestamp [UCT]: 2024-09-27 21:23:36 Age [y:d:h:m:s]: 00:168:20:52:15
Block: 1119503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120512 RingCT/type: yes/0
Extra: 01b87839555bd2a3c6b5582823580e697d7dd08f9228f9c4a4fa1e7c9fb1c31a3802110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0807ae642276dfc86397b251324bf6a0b021252add5ef030afb140810c2cc36 0.600000000000 1601082 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": 1119513, "vin": [ { "gen": { "height": 1119503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0807ae642276dfc86397b251324bf6a0b021252add5ef030afb140810c2cc36" } } ], "extra": [ 1, 184, 120, 57, 85, 91, 210, 163, 198, 181, 88, 40, 35, 88, 14, 105, 125, 125, 208, 143, 146, 40, 249, 196, 164, 250, 30, 124, 159, 177, 195, 26, 56, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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