Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 037946e0b9e3a40f9e3608f33d90f254237179257702dbc2ab175b2d24d073c7

Tx prefix hash: ea1f8db8c4ab47d556e753867c341cb2c9c97b47ce86c324ccca6023566e90fe
Tx public key: e696afbd327b5fb47b6a5304c3ba2e792f5b803220b4906723c892f1ce76aa03
Timestamp: 1732714329 Timestamp [UCT]: 2024-11-27 13:32:09 Age [y:d:h:m:s]: 00:118:23:54:46
Block: 1162865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84847 RingCT/type: yes/0
Extra: 01e696afbd327b5fb47b6a5304c3ba2e792f5b803220b4906723c892f1ce76aa030211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8adfcf012f9758f46ee65b5aadb681462e5b0ac267126749111b81bfbf29df90 0.600000000000 1648528 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": 1162875, "vin": [ { "gen": { "height": 1162865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8adfcf012f9758f46ee65b5aadb681462e5b0ac267126749111b81bfbf29df90" } } ], "extra": [ 1, 230, 150, 175, 189, 50, 123, 95, 180, 123, 106, 83, 4, 195, 186, 46, 121, 47, 91, 128, 50, 32, 180, 144, 103, 35, 200, 146, 241, 206, 118, 170, 3, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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