Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa588f62fec0b061b28397614b97ee1a3310a92def8880a89c5bd409dda6beed

Tx prefix hash: ca1db645fda0b1f7f9ef04043aa0564041f95dfdceeacbc7d96262e8b7d0c91a
Tx public key: eb63a860303a71a1a12af20f2f04d01e7f3e19681d13b8ed8f12cfa00081674b
Timestamp: 1680977853 Timestamp [UCT]: 2023-04-08 18:17:33 Age [y:d:h:m:s]: 02:004:11:21:37
Block: 734334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525303 RingCT/type: yes/0
Extra: 01eb63a860303a71a1a12af20f2f04d01e7f3e19681d13b8ed8f12cfa00081674b021100000005b3164c24000000000000000000

1 output(s) for total of 2.263845829000 dcy

stealth address amount amount idx
00: f66079a8a7a7e58b4a21730e96c630765d9bf2d86fd8a30296ca2b74d401c82e 2.263845829000 1180523 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": 734344, "vin": [ { "gen": { "height": 734334 } } ], "vout": [ { "amount": 2263845829, "target": { "key": "f66079a8a7a7e58b4a21730e96c630765d9bf2d86fd8a30296ca2b74d401c82e" } } ], "extra": [ 1, 235, 99, 168, 96, 48, 58, 113, 161, 161, 42, 242, 15, 47, 4, 208, 30, 127, 62, 25, 104, 29, 19, 184, 237, 143, 18, 207, 160, 0, 129, 103, 75, 2, 17, 0, 0, 0, 5, 179, 22, 76, 36, 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