Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0337fe3df262b78fa795efbf08ee072dceb8849deb22b0d4ef2d4fae34c689bf

Tx prefix hash: f6d7833f145cd1a3167cc01597e3bb2c395cccfd694ff43fde933d5ca36b6256
Tx public key: 8e819d347ca77cdcef4bd09d1b5f4065f29d87673e1a615f9e1bc16fa3e15010
Timestamp: 1737022436 Timestamp [UCT]: 2025-01-16 10:13:56 Age [y:d:h:m:s]: 01:010:06:40:25
Block: 1198526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265641 RingCT/type: yes/0
Extra: 018e819d347ca77cdcef4bd09d1b5f4065f29d87673e1a615f9e1bc16fa3e15010021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2808e0578234db72811cae73cdaa0db535ee21d5119a748bcc4eec6d6e2bfbe7 0.600000000000 1685151 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": 1198536, "vin": [ { "gen": { "height": 1198526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2808e0578234db72811cae73cdaa0db535ee21d5119a748bcc4eec6d6e2bfbe7" } } ], "extra": [ 1, 142, 129, 157, 52, 124, 167, 124, 220, 239, 75, 208, 157, 27, 95, 64, 101, 242, 157, 135, 103, 62, 26, 97, 95, 158, 27, 193, 111, 163, 225, 80, 16, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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