Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f8098f5e067072b771ce5470ceaa559a7542ecc740d1688b8adfc0b0838e9ca

Tx prefix hash: dce04c2e1379b8df01715ad29ed71e1901e38c21b7c32788b001624b6e9df61c
Tx public key: 08e6806f5f48027774d0d3905d3af0f8e44567c5c49f866892b5f83dba9c90b0
Timestamp: 1736094987 Timestamp [UCT]: 2025-01-05 16:36:27 Age [y:d:h:m:s]: 00:318:12:11:03
Block: 1190871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225140 RingCT/type: yes/0
Extra: 0108e6806f5f48027774d0d3905d3af0f8e44567c5c49f866892b5f83dba9c90b00211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c36caebd460716a80c1600b14d325e5e2f09e9922c627894cc5df78e471c2ab 0.600000000000 1677392 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": 1190881, "vin": [ { "gen": { "height": 1190871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c36caebd460716a80c1600b14d325e5e2f09e9922c627894cc5df78e471c2ab" } } ], "extra": [ 1, 8, 230, 128, 111, 95, 72, 2, 119, 116, 208, 211, 144, 93, 58, 240, 248, 228, 69, 103, 197, 196, 159, 134, 104, 146, 181, 248, 61, 186, 156, 144, 176, 2, 17, 0, 0, 0, 8, 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