Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 358404e94dc1fc6d7234c537bb6ab3eb5dff6c928d619ed1e851291d8a8464d2

Tx prefix hash: e25514579dbbf2da98d25d1488b5da877a53b68f73bd1e0118fcb2d880706b7b
Tx public key: 078005dea7daed0a78f278e1c35eb0bd4a0e82a359cd97470dd5b39165cf4ad5
Timestamp: 1706980276 Timestamp [UCT]: 2024-02-03 17:11:16 Age [y:d:h:m:s]: 01:099:02:28:58
Block: 949598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331923 RingCT/type: yes/0
Extra: 01078005dea7daed0a78f278e1c35eb0bd4a0e82a359cd97470dd5b39165cf4ad50211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c52ba35545c1b2c42ef9ef86fc851c0f3532c1794fd0dba19094eb3f051a241b 0.600000000000 1408128 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": 949608, "vin": [ { "gen": { "height": 949598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c52ba35545c1b2c42ef9ef86fc851c0f3532c1794fd0dba19094eb3f051a241b" } } ], "extra": [ 1, 7, 128, 5, 222, 167, 218, 237, 10, 120, 242, 120, 225, 195, 94, 176, 189, 74, 14, 130, 163, 89, 205, 151, 71, 13, 213, 179, 145, 101, 207, 74, 213, 2, 17, 0, 0, 0, 4, 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