Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0d34df9405cab4872aab88011be1ac8519ce1501c1f6eb4ac483d2a5efc3be2

Tx prefix hash: 25770570b610225bc38900d6d840b8d20c1b39b5fdb49efacdd4ed3d0927b50f
Tx public key: 20ec03c8439e7377ca5c72422a8ba1d00bed106f0a6ab3dc45e696855028ad14
Timestamp: 1724142623 Timestamp [UCT]: 2024-08-20 08:30:23 Age [y:d:h:m:s]: 00:237:03:07:47
Block: 1091904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169352 RingCT/type: yes/0
Extra: 0120ec03c8439e7377ca5c72422a8ba1d00bed106f0a6ab3dc45e696855028ad1402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e280f7bab974def859d2fe8a9a6e8068d7c9362b4c8c6b59a1a81fcdfde33702 0.600000000000 1566539 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": 1091914, "vin": [ { "gen": { "height": 1091904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e280f7bab974def859d2fe8a9a6e8068d7c9362b4c8c6b59a1a81fcdfde33702" } } ], "extra": [ 1, 32, 236, 3, 200, 67, 158, 115, 119, 202, 92, 114, 66, 42, 139, 161, 208, 11, 237, 16, 111, 10, 106, 179, 220, 69, 230, 150, 133, 80, 40, 173, 20, 2, 17, 0, 0, 0, 4, 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