Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c25de3346897dc25bf91e417d7f6ca8d12153743923b8f92654d60daf5c10976

Tx prefix hash: a8999a7c5951415889c5a772b09e7be42dd813c64bca3766ff6d06e54232aea1
Tx public key: b3a449674cd4ef410ecd97d79b8a5af47f870fb1d1d3610431ca1832457e79d4
Timestamp: 1709897640 Timestamp [UCT]: 2024-03-08 11:34:00 Age [y:d:h:m:s]: 01:066:09:27:46
Block: 973817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308465 RingCT/type: yes/0
Extra: 01b3a449674cd4ef410ecd97d79b8a5af47f870fb1d1d3610431ca1832457e79d402110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef658f45e422e89c62dd20078b64e066ec5fe7c0a5415ffda3801daa4d974407 0.600000000000 1433756 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": 973827, "vin": [ { "gen": { "height": 973817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef658f45e422e89c62dd20078b64e066ec5fe7c0a5415ffda3801daa4d974407" } } ], "extra": [ 1, 179, 164, 73, 103, 76, 212, 239, 65, 14, 205, 151, 215, 155, 138, 90, 244, 127, 135, 15, 177, 209, 211, 97, 4, 49, 202, 24, 50, 69, 126, 121, 212, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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