Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4d59f05aeea8188f22c1d069c1af7cc2ee4a712638a2fe5b014fb54373c2a8e

Tx prefix hash: 4cb07392d17cb77e71c9458adfd6144c41c1b86c000e91b1b09b8f265c928d8e
Tx public key: a04769eca76830c9658d447babb550322174992693ef1cc3457d48b8ea3bbbbd
Timestamp: 1765471040 Timestamp [UCT]: 2025-12-11 16:37:20 Age [y:d:h:m:s]: 00:050:05:31:48
Block: 1431393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35783 RingCT/type: yes/0
Extra: 01a04769eca76830c9658d447babb550322174992693ef1cc3457d48b8ea3bbbbd021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7156d84ec5dccf0eb390d64d1343d3850f70061bdd4e9a221ad5d68544473d5b 0.600000000000 1920160 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": 1431403, "vin": [ { "gen": { "height": 1431393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7156d84ec5dccf0eb390d64d1343d3850f70061bdd4e9a221ad5d68544473d5b" } } ], "extra": [ 1, 160, 71, 105, 236, 167, 104, 48, 201, 101, 141, 68, 123, 171, 181, 80, 50, 33, 116, 153, 38, 147, 239, 28, 195, 69, 125, 72, 184, 234, 59, 187, 189, 2, 17, 0, 0, 0, 2, 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