Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97e481b275e4cfaf413710cc92e9641a75e86641c58a13812a2ed97f8b605186

Tx prefix hash: 3415073d3d895a100aa216a42ea20cc2137b52f1d19f9fd00cb211538c8f0d83
Tx public key: 858d3a39a772dc1d83f66166d2624a5cfa80599edfa53403da3006c32d1c6d68
Timestamp: 1750398240 Timestamp [UCT]: 2025-06-20 05:44:00 Age [y:d:h:m:s]: 00:143:19:30:53
Block: 1308867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100588 RingCT/type: yes/0
Extra: 01858d3a39a772dc1d83f66166d2624a5cfa80599edfa53403da3006c32d1c6d680211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 259bf02d6dde5cc8329668cc7bc523d5a8fa965aa924d7a49c732365defdf4b6 0.600000000000 1796482 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": 1308877, "vin": [ { "gen": { "height": 1308867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "259bf02d6dde5cc8329668cc7bc523d5a8fa965aa924d7a49c732365defdf4b6" } } ], "extra": [ 1, 133, 141, 58, 57, 167, 114, 220, 29, 131, 246, 97, 102, 210, 98, 74, 92, 250, 128, 89, 158, 223, 165, 52, 3, 218, 48, 6, 195, 45, 28, 109, 104, 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