Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3afb079866d5ca814ce8b51186847d040cd6e75c6a405f4d0e2ccbd440f59db

Tx prefix hash: 20f1e61a0aeca9e3bf15b1fa8c77d9cca5d84cae27176919c315c98855c8ff31
Tx public key: 707cdf32289707c80f16bbb1616317d3ace8b94152a44ee3887a43d16cae239f
Timestamp: 1695500689 Timestamp [UCT]: 2023-09-23 20:24:49 Age [y:d:h:m:s]: 01:157:04:09:10
Block: 854642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373358 RingCT/type: yes/0
Extra: 01707cdf32289707c80f16bbb1616317d3ace8b94152a44ee3887a43d16cae239f021100000006faf35c9c000000000000000000

1 output(s) for total of 0.904099700000 dcy

stealth address amount amount idx
00: c5db3bbc9735827ea239a2a1237ef4be6abbd2946b70c6db0f616af481e1e12b 0.904099700000 1308626 of 0

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": 854652, "vin": [ { "gen": { "height": 854642 } } ], "vout": [ { "amount": 904099700, "target": { "key": "c5db3bbc9735827ea239a2a1237ef4be6abbd2946b70c6db0f616af481e1e12b" } } ], "extra": [ 1, 112, 124, 223, 50, 40, 151, 7, 200, 15, 22, 187, 177, 97, 99, 23, 211, 172, 232, 185, 65, 82, 164, 78, 227, 136, 122, 67, 209, 108, 174, 35, 159, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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