Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15244d2f577bbf7f993a2ce7a900f0730c3c2125ffca2b8bfa6b0e1c1c54d77f

Tx prefix hash: 5b4c567270b1254ac5bf49eb8eed2836a382a5292094bae765d3b14040f07fa4
Tx public key: 034446361f811e2f2aa3d01334f206d346f23012d76e562dd234cef780568420
Timestamp: 1707292224 Timestamp [UCT]: 2024-02-07 07:50:24 Age [y:d:h:m:s]: 00:340:18:35:39
Block: 952189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243969 RingCT/type: yes/0
Extra: 01034446361f811e2f2aa3d01334f206d346f23012d76e562dd234cef7805684200211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: efe4e83d037c114d018d41d9b3f1ac510a0e40bb88740af6a59a1cd189d6c1be 0.600010000000 1411073 of 0

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": 952199, "vin": [ { "gen": { "height": 952189 } } ], "vout": [ { "amount": 600010000, "target": { "key": "efe4e83d037c114d018d41d9b3f1ac510a0e40bb88740af6a59a1cd189d6c1be" } } ], "extra": [ 1, 3, 68, 70, 54, 31, 129, 30, 47, 42, 163, 208, 19, 52, 242, 6, 211, 70, 242, 48, 18, 215, 110, 86, 45, 210, 52, 206, 247, 128, 86, 132, 32, 2, 17, 0, 0, 0, 9, 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