Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 604c47ecdebfa0f3888711f12e2cc1dae65552ae07ea97f763d0f1b99e926d65

Tx prefix hash: f7a8fa531d267a8f539b559dcf5e9e80cbea1b3502769acd65698371dd42eaa0
Tx public key: 7f9cff2fcac96ec08b39d5447e05c6c5645d0673b4ad75dcd540a30cacecc492
Timestamp: 1708267528 Timestamp [UCT]: 2024-02-18 14:45:28 Age [y:d:h:m:s]: 00:341:09:06:51
Block: 960289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244330 RingCT/type: yes/0
Extra: 017f9cff2fcac96ec08b39d5447e05c6c5645d0673b4ad75dcd540a30cacecc49202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79c6ef9aaed10e868010dac2d54449521d5827ec4b354a2c55ada8aa00a87424 0.600000000000 1419852 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": 960299, "vin": [ { "gen": { "height": 960289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79c6ef9aaed10e868010dac2d54449521d5827ec4b354a2c55ada8aa00a87424" } } ], "extra": [ 1, 127, 156, 255, 47, 202, 201, 110, 192, 139, 57, 213, 68, 126, 5, 198, 197, 100, 93, 6, 115, 180, 173, 117, 220, 213, 64, 163, 12, 172, 236, 196, 146, 2, 17, 0, 0, 0, 2, 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