Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46283d3eda3f5d285f938e957ae2860d85f67df9c6e7889b8ae90537d3ab16a2

Tx prefix hash: b224bb9bca986fa7e35076d5e289da44fe22ff1ac20b797b6565ec56457b10bb
Tx public key: 4b6b39d524ed46c4a06c758a6615583391448c63a380528cdd88291047a7d3b1
Timestamp: 1716110527 Timestamp [UCT]: 2024-05-19 09:22:07 Age [y:d:h:m:s]: 00:281:20:13:17
Block: 1025318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201404 RingCT/type: yes/0
Extra: 014b6b39d524ed46c4a06c758a6615583391448c63a380528cdd88291047a7d3b10211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cf6235a5505d49b2a483f655e04b29fdd61ee10edf55cec8377a1b7ee4210b0 0.600000000000 1491731 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": 1025328, "vin": [ { "gen": { "height": 1025318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cf6235a5505d49b2a483f655e04b29fdd61ee10edf55cec8377a1b7ee4210b0" } } ], "extra": [ 1, 75, 107, 57, 213, 36, 237, 70, 196, 160, 108, 117, 138, 102, 21, 88, 51, 145, 68, 140, 99, 163, 128, 82, 140, 221, 136, 41, 16, 71, 167, 211, 177, 2, 17, 0, 0, 0, 9, 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