Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be87d13c61aab78fc7c866509ff4d2f5d6663c2dbbb59af52b68ef7258de877d

Tx prefix hash: df9a221f1a3a462436fee011af105b070baf9435840a7ecae3775f7ff225b198
Tx public key: 4b3ef4cc0f79598a77d628a3cfd5b45f28d71815e8fb35653fe272bbf05fa5bb
Timestamp: 1721878808 Timestamp [UCT]: 2024-07-25 03:40:08 Age [y:d:h:m:s]: 00:182:17:00:49
Block: 1073124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130681 RingCT/type: yes/0
Extra: 014b3ef4cc0f79598a77d628a3cfd5b45f28d71815e8fb35653fe272bbf05fa5bb02110000001ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8f9d885fb4f1ce90000affd3e1a888e144070983a6a7c3754bbdfe06c1de825 0.600000000000 1545623 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": 1073134, "vin": [ { "gen": { "height": 1073124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8f9d885fb4f1ce90000affd3e1a888e144070983a6a7c3754bbdfe06c1de825" } } ], "extra": [ 1, 75, 62, 244, 204, 15, 121, 89, 138, 119, 214, 40, 163, 207, 213, 180, 95, 40, 215, 24, 21, 232, 251, 53, 101, 63, 226, 114, 187, 240, 95, 165, 187, 2, 17, 0, 0, 0, 28, 233, 20, 221, 21, 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