Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5008149c4783e25ecb5a4e1c089ae6d9a53c193219dd1e6a457be3a7352b2b1d

Tx prefix hash: d02158b548521b235676d0912596a24dc5cb2bc9340754a03ee3534f4d7187f6
Tx public key: 03aa9bcbec61e4ffdf7173024008e874af814339dc4941ea0274156c63cb3cde
Timestamp: 1754574065 Timestamp [UCT]: 2025-08-07 13:41:05 Age [y:d:h:m:s]: 00:104:18:20:24
Block: 1342175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73932 RingCT/type: yes/0
Extra: 0103aa9bcbec61e4ffdf7173024008e874af814339dc4941ea0274156c63cb3cde021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd42e21dc0d0c9520119befd389f0bc3202c16b3221db8c870905cd0324ca8d8 0.600000000000 1830006 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": 1342185, "vin": [ { "gen": { "height": 1342175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd42e21dc0d0c9520119befd389f0bc3202c16b3221db8c870905cd0324ca8d8" } } ], "extra": [ 1, 3, 170, 155, 203, 236, 97, 228, 255, 223, 113, 115, 2, 64, 8, 232, 116, 175, 129, 67, 57, 220, 73, 65, 234, 2, 116, 21, 108, 99, 203, 60, 222, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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