Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: becba9a2716dd81cc2594f6f46da8fb4261388607cb0ec0bf33950c810717da1

Tx prefix hash: fef9c60b442f24028e03538614584225375bd71c43ca7b014c358f1657e4041b
Tx public key: 7f98df792033b0c42369314b9f5f69005704ec0a8e7524ca14c214a96c8a47f9
Timestamp: 1724031317 Timestamp [UCT]: 2024-08-19 01:35:17 Age [y:d:h:m:s]: 00:234:02:46:22
Block: 1090982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167194 RingCT/type: yes/0
Extra: 017f98df792033b0c42369314b9f5f69005704ec0a8e7524ca14c214a96c8a47f902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90197f6a6d536012468aa9f769b5ed45a05e9ff88ba42ed9be4622f686a8d7fe 0.600000000000 1565607 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": 1090992, "vin": [ { "gen": { "height": 1090982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90197f6a6d536012468aa9f769b5ed45a05e9ff88ba42ed9be4622f686a8d7fe" } } ], "extra": [ 1, 127, 152, 223, 121, 32, 51, 176, 196, 35, 105, 49, 75, 159, 95, 105, 0, 87, 4, 236, 10, 142, 117, 36, 202, 20, 194, 20, 169, 108, 138, 71, 249, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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