Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01e8ae80077d46f3d8f2a89fb74a4751aea9c4cea983654554aee65152d854f1

Tx prefix hash: ad62a7016266464168ffc462c190dd6e2a17ee25fd5cd32ec5529ba0c4214c39
Tx public key: fb96cf953169f716bdd5a1e8efb1c7699a2bc7133d7125fbf874e85d686768d5
Timestamp: 1710788511 Timestamp [UCT]: 2024-03-18 19:01:51 Age [y:d:h:m:s]: 01:262:04:34:44
Block: 981210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446096 RingCT/type: yes/0
Extra: 01fb96cf953169f716bdd5a1e8efb1c7699a2bc7133d7125fbf874e85d686768d502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f46c99226c42e008eb29e4d8b122eab0e4988d7f0e3cce4dca39d2f8e66040e9 0.600000000000 1441303 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": 981220, "vin": [ { "gen": { "height": 981210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f46c99226c42e008eb29e4d8b122eab0e4988d7f0e3cce4dca39d2f8e66040e9" } } ], "extra": [ 1, 251, 150, 207, 149, 49, 105, 247, 22, 189, 213, 161, 232, 239, 177, 199, 105, 154, 43, 199, 19, 61, 113, 37, 251, 248, 116, 232, 93, 104, 103, 104, 213, 2, 17, 0, 0, 0, 3, 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