Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f809aa306c506c67bd6d10e2e96779934ce8be034d15467d7e820dc5d6a7883d

Tx prefix hash: e7b37da0a9f0b7e2e418efd3fa35c78fdc4bbd6adad2fadb7c534225e74f0874
Tx public key: 6adea2469a825b7294a8123b6a3091a57905ea36ded4e160b2e913c899fd1ae2
Timestamp: 1715044729 Timestamp [UCT]: 2024-05-07 01:18:49 Age [y:d:h:m:s]: 00:338:04:38:00
Block: 1016487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241732 RingCT/type: yes/0
Extra: 016adea2469a825b7294a8123b6a3091a57905ea36ded4e160b2e913c899fd1ae20211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d92df3762914bb06a6c7203fe8655fa295f5bc2c74224f1ead44bb450b94220f 0.600000000000 1480084 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": 1016497, "vin": [ { "gen": { "height": 1016487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d92df3762914bb06a6c7203fe8655fa295f5bc2c74224f1ead44bb450b94220f" } } ], "extra": [ 1, 106, 222, 162, 70, 154, 130, 91, 114, 148, 168, 18, 59, 106, 48, 145, 165, 121, 5, 234, 54, 222, 212, 225, 96, 178, 233, 19, 200, 153, 253, 26, 226, 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