Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bda57af79a505888cf194a10107d76d418c0f942f9393472ae8eb69dc3b01fd

Tx prefix hash: 81f8705c6f3b57f8017effb3e41aa8f34cfa9ee20c61eeb1d2d89547d1dbf4f1
Tx public key: 94180a6448dd9a92e212fa18bf2e63fc7a627d2c438963c3cecc4986dec6063e
Timestamp: 1737181467 Timestamp [UCT]: 2025-01-18 06:24:27 Age [y:d:h:m:s]: 00:057:20:24:14
Block: 1199852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41122 RingCT/type: yes/0
Extra: 0194180a6448dd9a92e212fa18bf2e63fc7a627d2c438963c3cecc4986dec6063e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d7ec68548c312e31bec5efafecb5acbe38d46915daa53362d1216b5685e9e5d 0.600000000000 1686485 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": 1199862, "vin": [ { "gen": { "height": 1199852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d7ec68548c312e31bec5efafecb5acbe38d46915daa53362d1216b5685e9e5d" } } ], "extra": [ 1, 148, 24, 10, 100, 72, 221, 154, 146, 226, 18, 250, 24, 191, 46, 99, 252, 122, 98, 125, 44, 67, 137, 99, 195, 206, 204, 73, 134, 222, 198, 6, 62, 2, 17, 0, 0, 0, 5, 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