Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1e943d9879ef57806794e05d1dbcc7f5f5a405c0b93cb4ec54f796b640bd90c

Tx prefix hash: ac1f13dcc1b756225b0074d035344f9d1e6d0e7dcc7ad01f1420c5f51fd3a755
Tx public key: 79f79e83cbcce4e0187eb0678c91863ac6f129b4be1a73fcd904395839882da5
Timestamp: 1765779408 Timestamp [UCT]: 2025-12-15 06:16:48 Age [y:d:h:m:s]: 00:024:12:39:57
Block: 1433950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17569 RingCT/type: yes/0
Extra: 0179f79e83cbcce4e0187eb0678c91863ac6f129b4be1a73fcd904395839882da5021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9fc28f3213970de4e27bfb563b5c1968cd50f95ab6ba072d7e0e2d59df8b402 0.600000000000 1922731 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": 1433960, "vin": [ { "gen": { "height": 1433950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9fc28f3213970de4e27bfb563b5c1968cd50f95ab6ba072d7e0e2d59df8b402" } } ], "extra": [ 1, 121, 247, 158, 131, 203, 204, 228, 224, 24, 126, 176, 103, 140, 145, 134, 58, 198, 241, 41, 180, 190, 26, 115, 252, 217, 4, 57, 88, 57, 136, 45, 165, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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