Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d1d842afdef8aec5912db7a7b2b17c6ac3b057446828ddfff93c239fa0fdeb6

Tx prefix hash: d4688c9fe11ac4eea20566050437b88872b5059eb53bf6bf8ba5dbe83f96cb36
Tx public key: 5539945f0235e09fcb16db20f4b8b505b76cf86f5ce785e0fc17dd9fd1d99e8c
Timestamp: 1710678918 Timestamp [UCT]: 2024-03-17 12:35:18 Age [y:d:h:m:s]: 00:241:21:26:55
Block: 980300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173155 RingCT/type: yes/0
Extra: 015539945f0235e09fcb16db20f4b8b505b76cf86f5ce785e0fc17dd9fd1d99e8c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 264d17292bf4fba85de12829ae6ae2b3bc1a3a1595616b4037ebd715a4bf9c71 0.600000000000 1440365 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": 980310, "vin": [ { "gen": { "height": 980300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "264d17292bf4fba85de12829ae6ae2b3bc1a3a1595616b4037ebd715a4bf9c71" } } ], "extra": [ 1, 85, 57, 148, 95, 2, 53, 224, 159, 203, 22, 219, 32, 244, 184, 181, 5, 183, 108, 248, 111, 92, 231, 133, 224, 252, 23, 221, 159, 209, 217, 158, 140, 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