Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6d4d180bdf062e3e32063308a89d0d9a3c7c9c32f578790b14b5ab1bc30486d

Tx prefix hash: 3d201b19c14dfa999b999540f073c61eeaa9a5daeb3b0a1f6e8a01e11721e01d
Tx public key: c93c14f8f056724134b76cbbbf02a21b2139065cb1d70ba51280e47c53a0e922
Timestamp: 1764150937 Timestamp [UCT]: 2025-11-26 09:55:37 Age [y:d:h:m:s]: 00:027:01:55:38
Block: 1420455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19380 RingCT/type: yes/0
Extra: 01c93c14f8f056724134b76cbbbf02a21b2139065cb1d70ba51280e47c53a0e9220211000000034e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab055b097a2fa8bfc4c3a95cae7c20de07f090a453695fabf2aad3278de9b614 0.600000000000 1908998 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": 1420465, "vin": [ { "gen": { "height": 1420455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab055b097a2fa8bfc4c3a95cae7c20de07f090a453695fabf2aad3278de9b614" } } ], "extra": [ 1, 201, 60, 20, 248, 240, 86, 114, 65, 52, 183, 108, 187, 191, 2, 162, 27, 33, 57, 6, 92, 177, 215, 11, 165, 18, 128, 228, 124, 83, 160, 233, 34, 2, 17, 0, 0, 0, 3, 78, 123, 252, 9, 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