Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 857eac9c126336aebb0ef6c3d234a443592f17c8f2e8b65348a6a76e77002280

Tx prefix hash: 84d25ed4452375cec675fa779b6ae5e070cc878d28afbbeaa42ca6c47a86b713
Tx public key: 43392b56b17c93dbd075e912f8e0af16b5e730538a4c3171e80be2bf63238c3d
Timestamp: 1706482699 Timestamp [UCT]: 2024-01-28 22:58:19 Age [y:d:h:m:s]: 01:284:01:07:01
Block: 945464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461814 RingCT/type: yes/0
Extra: 0143392b56b17c93dbd075e912f8e0af16b5e730538a4c3171e80be2bf63238c3d0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84986214dc5e35fe574e3e26ba7ae4fedfdde7c9d1e59a31bfe64e2cf9de95c8 0.600000000000 1403778 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": 945474, "vin": [ { "gen": { "height": 945464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84986214dc5e35fe574e3e26ba7ae4fedfdde7c9d1e59a31bfe64e2cf9de95c8" } } ], "extra": [ 1, 67, 57, 43, 86, 177, 124, 147, 219, 208, 117, 233, 18, 248, 224, 175, 22, 181, 231, 48, 83, 138, 76, 49, 113, 232, 11, 226, 191, 99, 35, 140, 61, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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