Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16363b1450a733d362144f7adec753022d7bde9a528dea642aa5761257553b71

Tx prefix hash: f26b2ea0e510a69576b59e2e9b2e4e21a7cd07d1276ac2e952cb7acd589f170a
Tx public key: ca57d63c33266038a2d6e3e2118a591032948566f8cd5aaa92c9e6051b42d1be
Timestamp: 1685386377 Timestamp [UCT]: 2023-05-29 18:52:57 Age [y:d:h:m:s]: 01:235:16:36:19
Block: 770844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429837 RingCT/type: yes/0
Extra: 01ca57d63c33266038a2d6e3e2118a591032948566f8cd5aaa92c9e6051b42d1be02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.713460148000 dcy

stealth address amount amount idx
00: be823debfe1fa3214a300bde51aca5b0ce65adebc24d746abbdb6bb99044b0a8 1.713460148000 1220177 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": 770854, "vin": [ { "gen": { "height": 770844 } } ], "vout": [ { "amount": 1713460148, "target": { "key": "be823debfe1fa3214a300bde51aca5b0ce65adebc24d746abbdb6bb99044b0a8" } } ], "extra": [ 1, 202, 87, 214, 60, 51, 38, 96, 56, 162, 214, 227, 226, 17, 138, 89, 16, 50, 148, 133, 102, 248, 205, 90, 170, 146, 201, 230, 5, 27, 66, 209, 190, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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