Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f1b31b2e00c13c1e1909472cdbfbfd0546a2125b56cc470f5bebaff9d5aeda8

Tx prefix hash: dd0844f0470fc5948ab7c52a7ca6a3dd743cb928cfbe542e7e2c2009b6b79aa0
Tx public key: 7169eb77865e0249a207478b1174c8f707897caf6262af39b2f9f862d77a9a60
Timestamp: 1703451135 Timestamp [UCT]: 2023-12-24 20:52:15 Age [y:d:h:m:s]: 01:025:15:12:55
Block: 920357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279656 RingCT/type: yes/0
Extra: 017169eb77865e0249a207478b1174c8f707897caf6262af39b2f9f862d77a9a6002110000001059dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24ce08521417b58a9020c32bad5aa983e6a3818b901a3be7a34316f237116cb6 0.600000000000 1378035 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": 920367, "vin": [ { "gen": { "height": 920357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24ce08521417b58a9020c32bad5aa983e6a3818b901a3be7a34316f237116cb6" } } ], "extra": [ 1, 113, 105, 235, 119, 134, 94, 2, 73, 162, 7, 71, 139, 17, 116, 200, 247, 7, 137, 124, 175, 98, 98, 175, 57, 178, 249, 248, 98, 215, 122, 154, 96, 2, 17, 0, 0, 0, 16, 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