Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65d016224320c53506ce562017280d3bf60dbddb2d4aeb642b7a8f7a7d2e838f

Tx prefix hash: cef5f82ddb23a72e5f3b8db6a2cf91e4987802b3ad3c2980d1b083586407d8fd
Tx public key: 8efb7e24804e1c752dc1cee8d0725f3e948c5cacbe6bd4455cfbe03519a81077
Timestamp: 1715861363 Timestamp [UCT]: 2024-05-16 12:09:23 Age [y:d:h:m:s]: 00:326:10:34:35
Block: 1023247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233316 RingCT/type: yes/0
Extra: 018efb7e24804e1c752dc1cee8d0725f3e948c5cacbe6bd4455cfbe03519a8107702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d941040d6cf5314904d6f99c2a2272c856d7a34c7e6d95fa4a06bc2454ba27b 0.600000000000 1488092 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": 1023257, "vin": [ { "gen": { "height": 1023247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d941040d6cf5314904d6f99c2a2272c856d7a34c7e6d95fa4a06bc2454ba27b" } } ], "extra": [ 1, 142, 251, 126, 36, 128, 78, 28, 117, 45, 193, 206, 232, 208, 114, 95, 62, 148, 140, 92, 172, 190, 107, 212, 69, 92, 251, 224, 53, 25, 168, 16, 119, 2, 17, 0, 0, 0, 1, 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