Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c841a96cb5b435ef74758bb7b7a392ef238d8ccd74a9ee945114e14d1e9140b0

Tx prefix hash: 9daae754610119fd0208d8b72b20d18dac4c3bcc8b3dae50fa1d25fa43e334dc
Tx public key: fdf81dfc0ad21ef4e4bb8943da446f16e96fecc23b813cf45dc051b47c564d3e
Timestamp: 1717138235 Timestamp [UCT]: 2024-05-31 06:50:35 Age [y:d:h:m:s]: 00:309:02:56:15
Block: 1033833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220925 RingCT/type: yes/0
Extra: 01fdf81dfc0ad21ef4e4bb8943da446f16e96fecc23b813cf45dc051b47c564d3e02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac6196bc62a600db57ee09a858af1819ae401a350be736c72a4fc0c2c1007e59 0.600000000000 1502306 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": 1033843, "vin": [ { "gen": { "height": 1033833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac6196bc62a600db57ee09a858af1819ae401a350be736c72a4fc0c2c1007e59" } } ], "extra": [ 1, 253, 248, 29, 252, 10, 210, 30, 244, 228, 187, 137, 67, 218, 68, 111, 22, 233, 111, 236, 194, 59, 129, 60, 244, 93, 192, 81, 180, 124, 86, 77, 62, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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