Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8ff6673b475812cfdd22f22cb79a5fce785290478d4888dc6b1670547951fd7

Tx prefix hash: dc74b2c64d5930001e5a6ded1d75a2c3477fafd2f4f9fb636d8b62dad60643fb
Tx public key: 6670c6a1e09424409c4b6089335f3a4c6c79ff0bfa8bc878b851355373e08d3c
Timestamp: 1719199737 Timestamp [UCT]: 2024-06-24 03:28:57 Age [y:d:h:m:s]: 00:311:12:07:46
Block: 1050910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222627 RingCT/type: yes/0
Extra: 016670c6a1e09424409c4b6089335f3a4c6c79ff0bfa8bc878b851355373e08d3c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1268e94227514b340cd4890fd1216748df2f77c71cb699326b9a73e48027b400 0.600000000000 1521085 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": 1050920, "vin": [ { "gen": { "height": 1050910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1268e94227514b340cd4890fd1216748df2f77c71cb699326b9a73e48027b400" } } ], "extra": [ 1, 102, 112, 198, 161, 224, 148, 36, 64, 156, 75, 96, 137, 51, 95, 58, 76, 108, 121, 255, 11, 250, 139, 200, 120, 184, 81, 53, 83, 115, 224, 141, 60, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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