Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 801f5454a8ed15efbcd2e7b1daf5dacbb61dc2dec2577fc6e98250c813d3cd99

Tx prefix hash: cf77de819eb5757ad229463a904bdd696ebdd14e18855aadd4b4117b6d4ed229
Tx public key: c58e84e0034b6c52a1c7006d2d2d5765cfb44f5e11f20c62d6daa611e3d45739
Timestamp: 1762108997 Timestamp [UCT]: 2025-11-02 18:43:17 Age [y:d:h:m:s]: 00:050:21:53:56
Block: 1403527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36446 RingCT/type: yes/0
Extra: 01c58e84e0034b6c52a1c7006d2d2d5765cfb44f5e11f20c62d6daa611e3d457390211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f44a406a7d6507e28570ab91f5cb212b7179116b513372f3babfb093170c68ca 0.600000000000 1891874 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": 1403537, "vin": [ { "gen": { "height": 1403527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f44a406a7d6507e28570ab91f5cb212b7179116b513372f3babfb093170c68ca" } } ], "extra": [ 1, 197, 142, 132, 224, 3, 75, 108, 82, 161, 199, 0, 109, 45, 45, 87, 101, 207, 180, 79, 94, 17, 242, 12, 98, 214, 218, 166, 17, 227, 212, 87, 57, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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