Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a564c41d2151ef267addef450f93bc0d82f08f3666ee64083236bfbae15d9eb

Tx prefix hash: f3ffc76fd792225a31cb13c9225696b2be6fe78dc7fdeff1869d0576dcf7c891
Tx public key: ab9b9fa6c5d0d853a85604d65d2d8acf4d76431ccafb6015f6e2ee604b4753f1
Timestamp: 1725576316 Timestamp [UCT]: 2024-09-05 22:45:16 Age [y:d:h:m:s]: 00:125:06:01:18
Block: 1103793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89566 RingCT/type: yes/0
Extra: 01ab9b9fa6c5d0d853a85604d65d2d8acf4d76431ccafb6015f6e2ee604b4753f1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4437b0c7289c02ac3539c0cea38e7970ce71cef6e473fde811063fb305be402d 0.600000000000 1580758 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": 1103803, "vin": [ { "gen": { "height": 1103793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4437b0c7289c02ac3539c0cea38e7970ce71cef6e473fde811063fb305be402d" } } ], "extra": [ 1, 171, 155, 159, 166, 197, 208, 216, 83, 168, 86, 4, 214, 93, 45, 138, 207, 77, 118, 67, 28, 202, 251, 96, 21, 246, 226, 238, 96, 75, 71, 83, 241, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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