Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 051547bc2e3c1a42ed264b77acd90f56bfc2e8756bff261baa8373a001fb2411

Tx prefix hash: 33c73071f25c46c666503ad5c4805f40283360f28417fd9174fb3c9fde3b3f9c
Tx public key: fd81318e48cfb7fe02115b37dd83f56a2286e8567058b9050573e6e00b2b80dc
Timestamp: 1762492414 Timestamp [UCT]: 2025-11-07 05:13:34 Age [y:d:h:m:s]: 00:021:02:03:41
Block: 1406715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15097 RingCT/type: yes/0
Extra: 01fd81318e48cfb7fe02115b37dd83f56a2286e8567058b9050573e6e00b2b80dc02110000000501491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f95e3630a366623f8eae09007193d05cf832a8469412df1a38fbcb32b8e7eff7 0.600000000000 1895104 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": 1406725, "vin": [ { "gen": { "height": 1406715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f95e3630a366623f8eae09007193d05cf832a8469412df1a38fbcb32b8e7eff7" } } ], "extra": [ 1, 253, 129, 49, 142, 72, 207, 183, 254, 2, 17, 91, 55, 221, 131, 245, 106, 34, 134, 232, 86, 112, 88, 185, 5, 5, 115, 230, 224, 11, 43, 128, 220, 2, 17, 0, 0, 0, 5, 1, 73, 31, 136, 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