Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e476d802c57e63922579de096bb20c8056bdfd995e533c066a0261bcfcf2008f

Tx prefix hash: 3ffbf61c127f42659d9a86abd8db098a90ef77978984597e17e8aa10e4dc6fb1
Tx public key: 6fb5cc04e43944ce56ae0c7f9ef681eae19eb3e944c08c6f1de01bd493b5cb15
Timestamp: 1754744415 Timestamp [UCT]: 2025-08-09 13:00:15 Age [y:d:h:m:s]: 00:014:06:37:11
Block: 1343501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9403 RingCT/type: yes/0
Extra: 016fb5cc04e43944ce56ae0c7f9ef681eae19eb3e944c08c6f1de01bd493b5cb150211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea7e169f8c7bd1c479ceaffcd7fccf155f85371db7bf7c50fc93924a7260e328 0.600000000000 1831340 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": 1343511, "vin": [ { "gen": { "height": 1343501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea7e169f8c7bd1c479ceaffcd7fccf155f85371db7bf7c50fc93924a7260e328" } } ], "extra": [ 1, 111, 181, 204, 4, 228, 57, 68, 206, 86, 174, 12, 127, 158, 246, 129, 234, 225, 158, 179, 233, 68, 192, 140, 111, 29, 224, 27, 212, 147, 181, 203, 21, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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