Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6f2ba6bb99a9ddf738806fa0af58dee08b893db23859701f62109b35cad322b

Tx prefix hash: c999ef1e3a77269d3bf23ee8a0ae7ead1398a3f0e65bd20d130a25a2f89ca818
Tx public key: 21e05114e4d12fe7347c2a6c660c626193e76b5613bd3e6ad8b504202ae58f4c
Timestamp: 1709452590 Timestamp [UCT]: 2024-03-03 07:56:30 Age [y:d:h:m:s]: 01:073:14:24:00
Block: 970120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313616 RingCT/type: yes/0
Extra: 0121e05114e4d12fe7347c2a6c660c626193e76b5613bd3e6ad8b504202ae58f4c0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 154594eba7ac40a722ac506d28e36da649672c35f4a5a82526d3b23621366a16 0.600000000000 1429969 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": 970130, "vin": [ { "gen": { "height": 970120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "154594eba7ac40a722ac506d28e36da649672c35f4a5a82526d3b23621366a16" } } ], "extra": [ 1, 33, 224, 81, 20, 228, 209, 47, 231, 52, 124, 42, 108, 102, 12, 98, 97, 147, 231, 107, 86, 19, 189, 62, 106, 216, 181, 4, 32, 42, 229, 143, 76, 2, 17, 0, 0, 0, 5, 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