← previous blocknext block →recent activity
Analyzing
Block #94,292,249
10 transactions · 9 stateful · 2026-08-08 19:48:34 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,292,249 · 10 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
1w02w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d5a6305…73e9
0x34b655…2a6f
4 touches
1 conflict
0x1bee5aea…5f61
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0284b293…00a7
0x34b655…2a6f
2 touches
0 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
2 touches
0 conflicts
0x22c8341a…7f5f
0x34b655…2a6f
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 0x5d5a6305e5…b973e9
Audit this contract →
← previous block·next block →recent activity