Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc8b2ffaf9582614413c02d13e7f74c1d1e7e51cbf71e66216be3399158eddab

Tx prefix hash: ca6f8d43e9a00ab62e7ce4ef0444cef160c7569cf543a9cd60781f9c08c18d7e
Tx public key: 4cf2eb08f6448dfdcf2816e3fe8db04b4a6692ddc9e799fa1cad06cec0ec840c
Timestamp: 1705944000 Timestamp [UCT]: 2024-01-22 17:20:00 Age [y:d:h:m:s]: 01:288:18:36:36
Block: 940989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465190 RingCT/type: yes/0
Extra: 014cf2eb08f6448dfdcf2816e3fe8db04b4a6692ddc9e799fa1cad06cec0ec840c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58d3213c10f923c25d236b2d70b21c39b4f700194e38297d126796630897895a 0.600000000000 1399131 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": 940999, "vin": [ { "gen": { "height": 940989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58d3213c10f923c25d236b2d70b21c39b4f700194e38297d126796630897895a" } } ], "extra": [ 1, 76, 242, 235, 8, 246, 68, 141, 253, 207, 40, 22, 227, 254, 141, 176, 75, 74, 102, 146, 221, 201, 231, 153, 250, 28, 173, 6, 206, 192, 236, 132, 12, 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