Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffa68c30f7f7242a4245d19d8eff895a071ffa4f3c210d522c7dc70a979472d3

Tx prefix hash: 2adec35e6ab2cd5af8846aef0d52f02ada0c186747796ac0289d2102c59ba68c
Tx public key: bade3bb749e98565eebe5c938a87c0c64f90dc25f4e051655fba84ef9a89b46f
Timestamp: 1725225482 Timestamp [UCT]: 2024-09-01 21:18:02 Age [y:d:h:m:s]: 00:265:04:21:00
Block: 1100882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189411 RingCT/type: yes/0
Extra: 01bade3bb749e98565eebe5c938a87c0c64f90dc25f4e051655fba84ef9a89b46f02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38f0385f7201d005fc0b0e0c7a05d316b20842e01804becd69ef0be5aae9a769 0.600000000000 1576863 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": 1100892, "vin": [ { "gen": { "height": 1100882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38f0385f7201d005fc0b0e0c7a05d316b20842e01804becd69ef0be5aae9a769" } } ], "extra": [ 1, 186, 222, 59, 183, 73, 233, 133, 101, 238, 190, 92, 147, 138, 135, 192, 198, 79, 144, 220, 37, 244, 224, 81, 101, 95, 186, 132, 239, 154, 137, 180, 111, 2, 17, 0, 0, 0, 1, 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