← previous blocknext block →recent activity
Analyzing
Block #94,200,044
20 transactions · 18 stateful · 2026-08-08 12:01:18 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,200,044 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w49w512w013w118w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
14 touches
21 conflicts
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0x836544ae…79e6
0x34b655…2a6f
6 touches
3 conflicts
0xbe4a325a…ac1e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8765edd1…a7d5
0x34b655…2a6f
4 touches
1 conflict
0x8dfb88f5…5592
0x34b655…2a6f
4 touches
1 conflict
0x93ef53c7…f210
0x34b655…2a6f
4 touches
1 conflict
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
21 conflicts on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity