← previous blocknext block →recent activity
Analyzing
Block #94,226,246
12 transactions · 12 stateful · 2026-08-08 14:14:00 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,226,246 · 12 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
4w05w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd442ac37…1609
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x588380ee…0a5c
0x34b655…2a6f
4 touches
1 conflict
0xd7d3cccb…fd18
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xb245fe36…d765
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 0xd442ac3711…dd1609
Audit this contract →
← previous block·next block →recent activity