Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b28cfe9b3dd498e617d797e7bfdbbd144b1dc40de7968774b52511d16e045b5a

Tx prefix hash: 1a49a17f544d79b612687c2acce864d6ba654390ba1c76fd68bcf82875ff10be
Tx public key: 51f1f60f007e414d13b02ce65f63a21c4ba94b84c7313d9d814b25376895a7f0
Timestamp: 1702844300 Timestamp [UCT]: 2023-12-17 20:18:20 Age [y:d:h:m:s]: 01:170:01:19:07
Block: 915323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382722 RingCT/type: yes/0
Extra: 0151f1f60f007e414d13b02ce65f63a21c4ba94b84c7313d9d814b25376895a7f002110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8044ebd4b7dfbf5c856ea1db4ab637db357c1d984e498151ce761593f874a8bc 0.600000000000 1372717 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": 915333, "vin": [ { "gen": { "height": 915323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8044ebd4b7dfbf5c856ea1db4ab637db357c1d984e498151ce761593f874a8bc" } } ], "extra": [ 1, 81, 241, 246, 15, 0, 126, 65, 77, 19, 176, 44, 230, 95, 99, 162, 28, 75, 169, 75, 132, 199, 49, 61, 157, 129, 75, 37, 55, 104, 149, 167, 240, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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