← previous blocknext block →recent activity
Analyzing
Block #94,839,089
11 transactions · 10 stateful · 2026-08-10 17:49:39 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,839,089 · 11 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
1w02w13w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6af385b8…971b
0x34b655…2a6f
4 touches
1 conflict
0x6af385b8…971c
0x34b655…2a6f
4 touches
1 conflict
0x94b55f4a…57ea
0x34b655…2a6f
4 touches
1 conflict
0xa266b7e7…5749
0x34b655…2a6f
4 touches
1 conflict
0xcefb5333…67c6
0xd32edf…ff58
3 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0xdd40e13d…ffbc
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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: Perpl
1 conflict on slot 0x6af385b811…f6971b
Audit this contract →
← previous block·next block →recent activity