Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab50b1f77a98dfef407db81d8048ee764005c19567601ca75e6b52e7af56db98

Tx prefix hash: f26b2cf20f38d154469f0f91e9fa5c1214999571f03fa8adb9a3701405fbafec
Tx public key: cb4a3fd329cb99380c38b35f4b3d9ca389c1d0011f1a169a06de92cfd814e9d6
Timestamp: 1736843191 Timestamp [UCT]: 2025-01-14 08:26:31 Age [y:d:h:m:s]: 00:158:16:52:07
Block: 1197050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113072 RingCT/type: yes/0
Extra: 01cb4a3fd329cb99380c38b35f4b3d9ca389c1d0011f1a169a06de92cfd814e9d60211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb63080b301598465d173b7e040af2be039a68861db874a120beb2061f8e0ac6 0.600000000000 1683655 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": 1197060, "vin": [ { "gen": { "height": 1197050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb63080b301598465d173b7e040af2be039a68861db874a120beb2061f8e0ac6" } } ], "extra": [ 1, 203, 74, 63, 211, 41, 203, 153, 56, 12, 56, 179, 95, 75, 61, 156, 163, 137, 193, 208, 1, 31, 26, 22, 154, 6, 222, 146, 207, 216, 20, 233, 214, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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