Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dc59d3fe96481ca2e503c555fb66a1e72548055ed8c42621b3c0e8c3fc3bcb2

Tx prefix hash: 821df27f94709f16a2ac6861bba8fbf8391c1a5839afebb3fe27c9d037af7339
Tx public key: 5fef9f8e778a75c4cf5c719c44dca2cf0bce1772cd91b4a88486cf9e83f4a0d1
Timestamp: 1761664499 Timestamp [UCT]: 2025-10-28 15:14:59 Age [y:d:h:m:s]: 00:072:03:39:43
Block: 1399866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51653 RingCT/type: yes/0
Extra: 015fef9f8e778a75c4cf5c719c44dca2cf0bce1772cd91b4a88486cf9e83f4a0d1021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ad09eca97a3ff609fe4195c8eff8a73b6375a68914ca169101f773924f153dc 0.600000000000 1888171 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": 1399876, "vin": [ { "gen": { "height": 1399866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ad09eca97a3ff609fe4195c8eff8a73b6375a68914ca169101f773924f153dc" } } ], "extra": [ 1, 95, 239, 159, 142, 119, 138, 117, 196, 207, 92, 113, 156, 68, 220, 162, 207, 11, 206, 23, 114, 205, 145, 180, 168, 132, 134, 207, 158, 131, 244, 160, 209, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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