Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 873b63b4f2acb548e524206f932ad473d4093aa40eb730b9674db00181d4a2dc

Tx prefix hash: e934b5b6595ddd05aeb6dd295bd37a021ea4e813df9145db1f294bb078771b41
Tx public key: 5924af63224487de51903aee2900e45cd83f43d30c9c841fe7f900b531ea1da4
Timestamp: 1726676943 Timestamp [UCT]: 2024-09-18 16:29:03 Age [y:d:h:m:s]: 00:272:03:42:00
Block: 1112909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194269 RingCT/type: yes/0
Extra: 015924af63224487de51903aee2900e45cd83f43d30c9c841fe7f900b531ea1da4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d0fdf08fb67f7f57515f46ce6348b188451ebc511ce8e7ecb660ba5cbd95142 0.600000000000 1592396 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": 1112919, "vin": [ { "gen": { "height": 1112909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d0fdf08fb67f7f57515f46ce6348b188451ebc511ce8e7ecb660ba5cbd95142" } } ], "extra": [ 1, 89, 36, 175, 99, 34, 68, 135, 222, 81, 144, 58, 238, 41, 0, 228, 92, 216, 63, 67, 211, 12, 156, 132, 31, 231, 249, 0, 181, 49, 234, 29, 164, 2, 17, 0, 0, 0, 3, 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