Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee8a4e7a0f073a29b3d05703fe36c63371ad826bb92a8e21f0037b246ccfd851

Tx prefix hash: 4d1145fc1dc960ee857202d57a18b9715c4c802b9753a034e2680e47e5d7c9cb
Tx public key: 06ecc6251a34a7208137ba45ba678e2975813acca18fb8d14dd4f4ce1761291f
Timestamp: 1634940217 Timestamp [UCT]: 2021-10-22 22:03:37 Age [y:d:h:m:s]: 03:034:10:43:19
Block: 358394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 802895 RingCT/type: yes/0
Extra: 0106ecc6251a34a7208137ba45ba678e2975813acca18fb8d14dd4f4ce1761291f0211000000a18d0de867000000000000000000

1 output(s) for total of 39.855871765000 dcy

stealth address amount amount idx
00: b7c061eed78540ea6769d6ccec68232a2cb82ea64594d7253ea760affa4b22e7 39.855871765000 730283 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": 358404, "vin": [ { "gen": { "height": 358394 } } ], "vout": [ { "amount": 39855871765, "target": { "key": "b7c061eed78540ea6769d6ccec68232a2cb82ea64594d7253ea760affa4b22e7" } } ], "extra": [ 1, 6, 236, 198, 37, 26, 52, 167, 32, 129, 55, 186, 69, 186, 103, 142, 41, 117, 129, 58, 204, 161, 143, 184, 209, 77, 212, 244, 206, 23, 97, 41, 31, 2, 17, 0, 0, 0, 161, 141, 13, 232, 103, 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