Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f06e673ed27f1684f762c19867288f90a7d24efd74ffde41a7649ca9a6157e7

Tx prefix hash: bf789a9430bea3737d48c104bf7575b36ba034424b1ba8f4fb1766281f03083e
Tx public key: bec47c02c298293dd19bc956a259af2ed69f822e7a963fdcd12c1491d59e1f02
Timestamp: 1708793190 Timestamp [UCT]: 2024-02-24 16:46:30 Age [y:d:h:m:s]: 01:285:09:12:28
Block: 964658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462717 RingCT/type: yes/0
Extra: 01bec47c02c298293dd19bc956a259af2ed69f822e7a963fdcd12c1491d59e1f0202110000000239e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 543d6b39608c09a5ab4cff0ced6e04c3f116d2034c3aeb454eb12947d907269a 0.600000000000 1424399 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": 964668, "vin": [ { "gen": { "height": 964658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "543d6b39608c09a5ab4cff0ced6e04c3f116d2034c3aeb454eb12947d907269a" } } ], "extra": [ 1, 190, 196, 124, 2, 194, 152, 41, 61, 209, 155, 201, 86, 162, 89, 175, 46, 214, 159, 130, 46, 122, 150, 63, 220, 209, 44, 20, 145, 213, 158, 31, 2, 2, 17, 0, 0, 0, 2, 57, 225, 213, 211, 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