Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1acbd9ac1a0a501e2fc592517a26acc8e620a8ebe8f0818d50372080d26981ba

Tx prefix hash: 8ad33dd2fbf191978ebc8a1b87d6fc6bda0f3c5feb3157a50e7bf61efc324237
Tx public key: a2e8d34291ed9053af284b84b3eea788968c462e3373a46b9db91742e498ea17
Timestamp: 1728205508 Timestamp [UCT]: 2024-10-06 09:05:08 Age [y:d:h:m:s]: 00:032:16:07:17
Block: 1125590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23309 RingCT/type: yes/0
Extra: 01a2e8d34291ed9053af284b84b3eea788968c462e3373a46b9db91742e498ea1702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f59c2af3011ae8a5100aa7bd456327e86e9117b5d0718f82f8cfda9437fef8df 0.600000000000 1608341 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": 1125600, "vin": [ { "gen": { "height": 1125590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f59c2af3011ae8a5100aa7bd456327e86e9117b5d0718f82f8cfda9437fef8df" } } ], "extra": [ 1, 162, 232, 211, 66, 145, 237, 144, 83, 175, 40, 75, 132, 179, 238, 167, 136, 150, 140, 70, 46, 51, 115, 164, 107, 157, 185, 23, 66, 228, 152, 234, 23, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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