Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfaee41ba74de0fb98f98ab53a71b7d57cc1ba43dc41c726a198185e3cba3807

Tx prefix hash: 1da044da804bfaaec1ce34ece10b489af2d6b8bef174bda24a0952ed93c977e8
Tx public key: bf983ec8a60dc21ebe889b7079a7e43a4f080ae08496c8a0ea04a654c9938877
Timestamp: 1720180632 Timestamp [UCT]: 2024-07-05 11:57:12 Age [y:d:h:m:s]: 00:259:19:05:32
Block: 1059045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185622 RingCT/type: yes/0
Extra: 01bf983ec8a60dc21ebe889b7079a7e43a4f080ae08496c8a0ea04a654c99388770211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acd35247ac6a8358ca3a6683b98cf743c3d163d3b641615c6aa4a5d501209394 0.600000000000 1529504 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": 1059055, "vin": [ { "gen": { "height": 1059045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acd35247ac6a8358ca3a6683b98cf743c3d163d3b641615c6aa4a5d501209394" } } ], "extra": [ 1, 191, 152, 62, 200, 166, 13, 194, 30, 190, 136, 155, 112, 121, 167, 228, 58, 79, 8, 10, 224, 132, 150, 200, 160, 234, 4, 166, 84, 201, 147, 136, 119, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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