Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65a56413603991586108c172be608339e900be25ec946a09b9fce5f7c8896655

Tx prefix hash: 73a658797ee48cd0ca3b0cd38fe8725932a411483b53b42a3dc6a72fcbccd4f8
Tx public key: 7ad7ce45e0e4d592f750a41e1cbb9070bacebf5d0a6a5091a9803b6bef3ae0cc
Timestamp: 1740956559 Timestamp [UCT]: 2025-03-02 23:02:39 Age [y:d:h:m:s]: 00:010:10:59:27
Block: 1230833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7497 RingCT/type: yes/0
Extra: 017ad7ce45e0e4d592f750a41e1cbb9070bacebf5d0a6a5091a9803b6bef3ae0cc02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8226d8f4373a5d150161b293dda2c8b8db489abc839e68cdaaf47062f8cb35e 0.600000000000 1717736 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": 1230843, "vin": [ { "gen": { "height": 1230833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8226d8f4373a5d150161b293dda2c8b8db489abc839e68cdaaf47062f8cb35e" } } ], "extra": [ 1, 122, 215, 206, 69, 224, 228, 213, 146, 247, 80, 164, 30, 28, 187, 144, 112, 186, 206, 191, 93, 10, 106, 80, 145, 169, 128, 59, 107, 239, 58, 224, 204, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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