Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfe99f9198b8bb8892211610fd2388c55fe3922a3f2a01eefa5d4bc309743c6b

Tx prefix hash: d401fe87a1c45529cb4014fa27a082b56887d5649af57d7df1a3b3e974640db9
Tx public key: c3079679c104e0f6b8f8c0785169b8e3bb80ff1f41949aee48a6c279d4f74ccd
Timestamp: 1578892335 Timestamp [UCT]: 2020-01-13 05:12:15 Age [y:d:h:m:s]: 05:126:08:30:30
Block: 44382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1240541 RingCT/type: yes/0
Extra: 01c3079679c104e0f6b8f8c0785169b8e3bb80ff1f41949aee48a6c279d4f74ccd02110000000bd81c26c0000000000000000000

1 output(s) for total of 437.466550196000 dcy

stealth address amount amount idx
00: f03ecd56be7780f3cd578fb3d8cc2492f5eea55f55f1f1ca8d07b4ff04aa23f4 437.466550196000 80748 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": 44392, "vin": [ { "gen": { "height": 44382 } } ], "vout": [ { "amount": 437466550196, "target": { "key": "f03ecd56be7780f3cd578fb3d8cc2492f5eea55f55f1f1ca8d07b4ff04aa23f4" } } ], "extra": [ 1, 195, 7, 150, 121, 193, 4, 224, 246, 184, 248, 192, 120, 81, 105, 184, 227, 187, 128, 255, 31, 65, 148, 154, 238, 72, 166, 194, 121, 212, 247, 76, 205, 2, 17, 0, 0, 0, 11, 216, 28, 38, 192, 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