Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 392923f8016f67b76bdb865e5affbf2dc8617ab6c0d138fd40ed178b914ca186

Tx prefix hash: 7e381da90170d74187bd10e5bb4695d40609d84a307ecebb510cc2cb7912c9b2
Tx public key: 0e70d0f9273ab69444360776f67dcd1c1f22724f9fb6ee32cfe2fe3e97de47cb
Timestamp: 1724874735 Timestamp [UCT]: 2024-08-28 19:52:15 Age [y:d:h:m:s]: 00:221:19:23:43
Block: 1097967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158383 RingCT/type: yes/0
Extra: 010e70d0f9273ab69444360776f67dcd1c1f22724f9fb6ee32cfe2fe3e97de47cb02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da08f5aa7f2a4fef26436b4b9d5425d51c45d78184cb72a3ac7354fdbcf85713 0.600000000000 1573520 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": 1097977, "vin": [ { "gen": { "height": 1097967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da08f5aa7f2a4fef26436b4b9d5425d51c45d78184cb72a3ac7354fdbcf85713" } } ], "extra": [ 1, 14, 112, 208, 249, 39, 58, 182, 148, 68, 54, 7, 118, 246, 125, 205, 28, 31, 34, 114, 79, 159, 182, 238, 50, 207, 226, 254, 62, 151, 222, 71, 203, 2, 17, 0, 0, 0, 2, 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