Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c41b91c792ad4920def801bd128233e64531eb6b76f8283432b9851cc99f0686

Tx prefix hash: 69efa5f0b7e1d1088addd94c0181f0e2888fc8be3c43226a0e2d660ad07d233a
Tx public key: 4da8fd5ebaa29a76f41011c49ba67bb89a4df6dc035714ab0100c186142ad153
Timestamp: 1695904721 Timestamp [UCT]: 2023-09-28 12:38:41 Age [y:d:h:m:s]: 01:194:09:35:21
Block: 858001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399986 RingCT/type: yes/0
Extra: 014da8fd5ebaa29a76f41011c49ba67bb89a4df6dc035714ab0100c186142ad15302110000000afaf35c9c000000000000000000

1 output(s) for total of 0.881224491000 dcy

stealth address amount amount idx
00: de60752a5a8fd49d92e2a567aae3d5db66753c699a4cd6499d01a7a070ba454c 0.881224491000 1312155 of 0

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": 858011, "vin": [ { "gen": { "height": 858001 } } ], "vout": [ { "amount": 881224491, "target": { "key": "de60752a5a8fd49d92e2a567aae3d5db66753c699a4cd6499d01a7a070ba454c" } } ], "extra": [ 1, 77, 168, 253, 94, 186, 162, 154, 118, 244, 16, 17, 196, 155, 166, 123, 184, 154, 77, 246, 220, 3, 87, 20, 171, 1, 0, 193, 134, 20, 42, 209, 83, 2, 17, 0, 0, 0, 10, 250, 243, 92, 156, 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