Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c77bd598a8e7eba23984aceb23df9b57426278c3b31e8504f7b5477f3b20f077

Tx prefix hash: a7284b0091133ae4535e9c8b80c077ea96c0cddd08569195a26815be71aabfab
Tx public key: 36b0a519730bad5248aadc4f4573e1606f1d37fb9e307a60d17a8502edb6ebc2
Timestamp: 1702886014 Timestamp [UCT]: 2023-12-18 07:53:34 Age [y:d:h:m:s]: 01:331:04:34:14
Block: 915670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495557 RingCT/type: yes/0
Extra: 0136b0a519730bad5248aadc4f4573e1606f1d37fb9e307a60d17a8502edb6ebc202110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e4827047a3f4bf009126d71c382814c86faaa6e84ca2fde040ffc53dcbc514d 0.600000000000 1373076 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": 915680, "vin": [ { "gen": { "height": 915670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e4827047a3f4bf009126d71c382814c86faaa6e84ca2fde040ffc53dcbc514d" } } ], "extra": [ 1, 54, 176, 165, 25, 115, 11, 173, 82, 72, 170, 220, 79, 69, 115, 225, 96, 111, 29, 55, 251, 158, 48, 122, 96, 209, 122, 133, 2, 237, 182, 235, 194, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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