Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4de89a5a6fa8238ce7a0e387a29791aed9deaf6ab5ccaf0f96fc8d94743268b5

Tx prefix hash: 23eab30e97778a72404541fe3bafafc3cda622b03cf569b188c1cc973e978135
Tx public key: 66c3f63541adaf84ce69622c8ac24b517df908984fd013dd63d0c11dab5c8a2d
Timestamp: 1707012998 Timestamp [UCT]: 2024-02-04 02:16:38 Age [y:d:h:m:s]: 00:347:04:23:08
Block: 949875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248544 RingCT/type: yes/0
Extra: 0166c3f63541adaf84ce69622c8ac24b517df908984fd013dd63d0c11dab5c8a2d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c015200f051ffb3b1fae932a9f1c9adb51b5587e692d49f2e005727f2d9b8103 0.600000000000 1408409 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": 949885, "vin": [ { "gen": { "height": 949875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c015200f051ffb3b1fae932a9f1c9adb51b5587e692d49f2e005727f2d9b8103" } } ], "extra": [ 1, 102, 195, 246, 53, 65, 173, 175, 132, 206, 105, 98, 44, 138, 194, 75, 81, 125, 249, 8, 152, 79, 208, 19, 221, 99, 208, 193, 29, 171, 92, 138, 45, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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