Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5db762fd9039a25f8bc92c52c3ffc8b38c73972d0a500cb6e76ee743e199062

Tx prefix hash: a4d2a769282078e6e0e5fffa4395be53187e8ac722c3c04ca58dd6b325e11ed9
Tx public key: ff8e492c49b19f2a7a7e30efb68d23c7514e20753f331a3a641ae4c7455fb0d5
Timestamp: 1711340761 Timestamp [UCT]: 2024-03-25 04:26:01 Age [y:d:h:m:s]: 01:020:11:01:24
Block: 985789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275578 RingCT/type: yes/0
Extra: 01ff8e492c49b19f2a7a7e30efb68d23c7514e20753f331a3a641ae4c7455fb0d50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05f7deb30919e7b07d1a20d2850805dcdb197c42cf56da97253fe07634e52afb 0.600000000000 1446008 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": 985799, "vin": [ { "gen": { "height": 985789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05f7deb30919e7b07d1a20d2850805dcdb197c42cf56da97253fe07634e52afb" } } ], "extra": [ 1, 255, 142, 73, 44, 73, 177, 159, 42, 122, 126, 48, 239, 182, 141, 35, 199, 81, 78, 32, 117, 63, 51, 26, 58, 100, 26, 228, 199, 69, 95, 176, 213, 2, 17, 0, 0, 0, 1, 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