Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99159e64f8a65e4655cb1b8cb411f1cc0719ab2d3961a89231719c07c44a0ec8

Tx prefix hash: 767e9ba91641dc41c0d2f6434fe209c3dc1451c9738573c48d8516b6e060f418
Tx public key: 97dac7fc2230767ffdbff134a77c435eb38b8869c78e2e7f549b688625b6a667
Timestamp: 1718891209 Timestamp [UCT]: 2024-06-20 13:46:49 Age [y:d:h:m:s]: 00:205:03:51:32
Block: 1048365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146810 RingCT/type: yes/0
Extra: 0197dac7fc2230767ffdbff134a77c435eb38b8869c78e2e7f549b688625b6a66702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 010e8ee77ef8e8c84ba2998caef9d815e1b83f66389029f1debc206e8a29a580 0.600000000000 1518434 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": 1048375, "vin": [ { "gen": { "height": 1048365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "010e8ee77ef8e8c84ba2998caef9d815e1b83f66389029f1debc206e8a29a580" } } ], "extra": [ 1, 151, 218, 199, 252, 34, 48, 118, 127, 253, 191, 241, 52, 167, 124, 67, 94, 179, 139, 136, 105, 199, 142, 46, 127, 84, 155, 104, 134, 37, 182, 166, 103, 2, 17, 0, 0, 0, 3, 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