Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fb394b28ca493ecb3bcb88986fc4c758701cc614537f890eb1490a2f16010be

Tx prefix hash: a9f859c693623a2958f7bdf0691ebe407b7848a1663da251347c9be0ef958f6c
Tx public key: ab5fdb237bc1838c8d5a59c75a25f8965f3222ec130bc57c75ba68ca4c8bd2f1
Timestamp: 1711249508 Timestamp [UCT]: 2024-03-24 03:05:08 Age [y:d:h:m:s]: 01:033:05:10:39
Block: 985029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284706 RingCT/type: yes/0
Extra: 01ab5fdb237bc1838c8d5a59c75a25f8965f3222ec130bc57c75ba68ca4c8bd2f10211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9be232dd1f1f1d0bdc8a3facf3e39a2fa3c11f50adee63b32a1f4d48d57f7de 0.600000000000 1445234 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": 985039, "vin": [ { "gen": { "height": 985029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9be232dd1f1f1d0bdc8a3facf3e39a2fa3c11f50adee63b32a1f4d48d57f7de" } } ], "extra": [ 1, 171, 95, 219, 35, 123, 193, 131, 140, 141, 90, 89, 199, 90, 37, 248, 150, 95, 50, 34, 236, 19, 11, 197, 124, 117, 186, 104, 202, 76, 139, 210, 241, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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