Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4363aee8d8fe8f40c1a6572221e39d9a842839eb36bbf1b027b1e88c1df4fea

Tx prefix hash: 3e285197525e0119a6a3915b68b3b737377caf0d67c726f94245d983aea00636
Tx public key: d40e9c7bef10ae442828de30ca4d7987e4da9dbedaeecf019948fb14af9db354
Timestamp: 1765551729 Timestamp [UCT]: 2025-12-12 15:02:09 Age [y:d:h:m:s]: 00:029:05:21:19
Block: 1432069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20936 RingCT/type: yes/0
Extra: 01d40e9c7bef10ae442828de30ca4d7987e4da9dbedaeecf019948fb14af9db354021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6be110b535f28f8d7705e36ce26943d702e3ea0746d872e6270aef70dc84936 0.600000000000 1920848 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": 1432079, "vin": [ { "gen": { "height": 1432069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6be110b535f28f8d7705e36ce26943d702e3ea0746d872e6270aef70dc84936" } } ], "extra": [ 1, 212, 14, 156, 123, 239, 16, 174, 68, 40, 40, 222, 48, 202, 77, 121, 135, 228, 218, 157, 190, 218, 238, 207, 1, 153, 72, 251, 20, 175, 157, 179, 84, 2, 17, 0, 0, 0, 3, 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