← previous blocknext block →recent activity
Analyzing
Block #94,209,347
11 transactions · 8 stateful · 2026-08-08 12:48:22 UTC
Parallelism
73/100
Blocked
25%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,209,347 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x61d37f4f…61d2
0x34b655…2a6f
4 touches
1 conflict
0xc91d4275…1d7c
0x34b655…2a6f
4 touches
1 conflict
0x0b9b07b8…b998
0x34b655…2a6f
4 touches
1 conflict
0x7f4a8466…f2cc
0x2b46c0…1669
2 touches
0 conflicts
0xbca4de0c…577c
0x34b655…2a6f
2 touches
0 conflicts
0xc2db6e7a…d074
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
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity