Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f285b0b037175a1ab2399ffc40c46fa1e8be96c021ccf260cf89ca9f3829fd5

Tx prefix hash: 93f432eab8bc47a50546297be2fd9c2609aa814c945d85cd591586a38fd5c75f
Tx public key: ab522f674120d17c28090a15a3e76013e1b3183a5a1d10f02938cedc896305dc
Timestamp: 1736087540 Timestamp [UCT]: 2025-01-05 14:32:20 Age [y:d:h:m:s]: 00:130:14:16:48
Block: 1190802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93131 RingCT/type: yes/0
Extra: 01ab522f674120d17c28090a15a3e76013e1b3183a5a1d10f02938cedc896305dc02110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35493364291df78b153921dc9ae68aee905714a6e5b281e996867e36a65b467d 0.600000000000 1677321 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": 1190812, "vin": [ { "gen": { "height": 1190802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35493364291df78b153921dc9ae68aee905714a6e5b281e996867e36a65b467d" } } ], "extra": [ 1, 171, 82, 47, 103, 65, 32, 209, 124, 40, 9, 10, 21, 163, 231, 96, 19, 225, 179, 24, 58, 90, 29, 16, 240, 41, 56, 206, 220, 137, 99, 5, 220, 2, 17, 0, 0, 0, 13, 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