Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7fcb0962329ff05edb5e677b7802e3c838562eb1473bc2f0f5cdcb749815f3c

Tx prefix hash: 7ba6e2d053e03409bbb8fcc41caa6fd2c1dae459445dc8c73738b91a40308d2b
Tx public key: 42f500cd961574139d720ed1b3df5b8c8a5d0b4fce6ae158fa0b8b813e73361f
Timestamp: 1705695495 Timestamp [UCT]: 2024-01-19 20:18:15 Age [y:d:h:m:s]: 01:077:20:24:35
Block: 938930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316741 RingCT/type: yes/0
Extra: 0142f500cd961574139d720ed1b3df5b8c8a5d0b4fce6ae158fa0b8b813e73361f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91821f1784804e85fc5411365ec6db33d233ebb97e61c5b0f27f271e591735a8 0.600000000000 1397012 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": 938940, "vin": [ { "gen": { "height": 938930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91821f1784804e85fc5411365ec6db33d233ebb97e61c5b0f27f271e591735a8" } } ], "extra": [ 1, 66, 245, 0, 205, 150, 21, 116, 19, 157, 114, 14, 209, 179, 223, 91, 140, 138, 93, 11, 79, 206, 106, 225, 88, 250, 11, 139, 129, 62, 115, 54, 31, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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