Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f51d779372e9c71dc7cae13b9b944cc0d47c4d6bab8958c02ed001ad7dd5b4bf

Tx prefix hash: 4451e038669c42e1d2e4e181bd7d6325d10ce5b5dc5fc0cf36195c7febff3b6f
Tx public key: e86527898133daca7fdacd6323ec91e8fbbd0b2c5f48b8669159422fbcd86f3e
Timestamp: 1764004309 Timestamp [UCT]: 2025-11-24 17:11:49 Age [y:d:h:m:s]: 00:003:00:48:54
Block: 1419244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2179 RingCT/type: yes/0
Extra: 01e86527898133daca7fdacd6323ec91e8fbbd0b2c5f48b8669159422fbcd86f3e021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6116fc7f55a8a46e3a3598bba67754302f3a65ba43cbd2ace9d5a12ca7015b60 0.600000000000 1907779 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": 1419254, "vin": [ { "gen": { "height": 1419244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6116fc7f55a8a46e3a3598bba67754302f3a65ba43cbd2ace9d5a12ca7015b60" } } ], "extra": [ 1, 232, 101, 39, 137, 129, 51, 218, 202, 127, 218, 205, 99, 35, 236, 145, 232, 251, 189, 11, 44, 95, 72, 184, 102, 145, 89, 66, 47, 188, 216, 111, 62, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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