Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6de23fda6e42efb4e87cbf0e041b7434eb1e7dc2176f575f4196484583a7d026

Tx prefix hash: dd62aba0a2604d04b342c87d36f9fcab446e6d79b4347e146770eb457e03bfd6
Tx public key: dd59635df1fd70dd218880d6641f49a38be2607226defab0734014a14f9c751c
Timestamp: 1721828916 Timestamp [UCT]: 2024-07-24 13:48:36 Age [y:d:h:m:s]: 00:254:06:17:43
Block: 1072708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181635 RingCT/type: yes/0
Extra: 01dd59635df1fd70dd218880d6641f49a38be2607226defab0734014a14f9c751c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c852b7a4bdaff4933db465eae3d018ab1c0c4a5d89c6a0be2cb1db5f54163d50 0.600000000000 1545199 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": 1072718, "vin": [ { "gen": { "height": 1072708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c852b7a4bdaff4933db465eae3d018ab1c0c4a5d89c6a0be2cb1db5f54163d50" } } ], "extra": [ 1, 221, 89, 99, 93, 241, 253, 112, 221, 33, 136, 128, 214, 100, 31, 73, 163, 139, 226, 96, 114, 38, 222, 250, 176, 115, 64, 20, 161, 79, 156, 117, 28, 2, 17, 0, 0, 0, 5, 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