Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 291cd9dfc3ea9a6515fa629c34b6b4a1dd14dfe5d30f626b0609778d7b10457b

Tx prefix hash: 45456edb42a13024aff9e1770ebd6c7d2d3c39010866553067ce341457d6402c
Tx public key: 05f4c7e2d75032539e120d05f7926b8ab2b4c269de29eb9f8ca4e6286d154e64
Timestamp: 1703079142 Timestamp [UCT]: 2023-12-20 13:32:22 Age [y:d:h:m:s]: 01:144:22:50:17
Block: 917272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364745 RingCT/type: yes/0
Extra: 0105f4c7e2d75032539e120d05f7926b8ab2b4c269de29eb9f8ca4e6286d154e6402110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0865c33c0556f8c842a591d9ae015faf31403a06c678a1564ab709523421cab0 0.600000000000 1374842 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": 917282, "vin": [ { "gen": { "height": 917272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0865c33c0556f8c842a591d9ae015faf31403a06c678a1564ab709523421cab0" } } ], "extra": [ 1, 5, 244, 199, 226, 215, 80, 50, 83, 158, 18, 13, 5, 247, 146, 107, 138, 178, 180, 194, 105, 222, 41, 235, 159, 140, 164, 230, 40, 109, 21, 78, 100, 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