Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b38a68b2493605476da88f6feb7f9d42afdbae4087c6bc1100c0c15b784ec7c

Tx prefix hash: 893e186943d394e4c126d4f0e703fa8188d9cf38fe5a80a182ba427629d75944
Tx public key: 9f034664a6a9ef0c9eec64afbd3b98065c6aa2d19dda9102a34371edf6a3e51d
Timestamp: 1717116346 Timestamp [UCT]: 2024-05-31 00:45:46 Age [y:d:h:m:s]: 00:153:14:34:44
Block: 1033647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109950 RingCT/type: yes/0
Extra: 019f034664a6a9ef0c9eec64afbd3b98065c6aa2d19dda9102a34371edf6a3e51d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7b305784b30653ade3dc129b193f63fcb5b6442fa87a6b4e8837932ed35158b 0.600000000000 1502118 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": 1033657, "vin": [ { "gen": { "height": 1033647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7b305784b30653ade3dc129b193f63fcb5b6442fa87a6b4e8837932ed35158b" } } ], "extra": [ 1, 159, 3, 70, 100, 166, 169, 239, 12, 158, 236, 100, 175, 189, 59, 152, 6, 92, 106, 162, 209, 157, 218, 145, 2, 163, 67, 113, 237, 246, 163, 229, 29, 2, 17, 0, 0, 0, 3, 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