← previous blocknext block →recent activity
Analyzing
Block #94,836,105
20 transactions · 17 stateful · 2026-08-10 17:34:38 UTC
Parallelism
90/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,836,105 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w110w011w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x00000000…0002
0xeae24c…0be0
4 touches
1 conflict
0x1f0f4ea8…b66e
0x065c9d…c394
2 touches
0 conflicts
0x2b2e8694…d4f7
0x065c9d…c394
2 touches
0 conflicts
0x3e5741af…a03c
0x065c9d…c394
2 touches
0 conflicts
0xe4b2a275…bd83
0x065c9d…c394
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0xb33ff82315…a81188
Audit this contract →
← previous block·next block →recent activity