← previous blocknext block →recent activity
Analyzing
Block #94,914,867
14 transactions · 12 stateful · 2026-08-11 00:10:47 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,914,867 · 14 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
3w05w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb39cb1d8…effa
0x34b655…2a6f
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x28b01e5f…ced5
0x2880ab…7b43
2 touches
0 conflicts
0x28b01e5f…ced6
0x2880ab…7b43
2 touches
0 conflicts
0x9f3dfa2c…d6d5
0x2880ab…7b43
2 touches
0 conflicts
0x9f3dfa2c…d6d6
0x2880ab…7b43
2 touches
0 conflicts
0xa367eff3…1905
0x2880ab…7b43
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 0xb39cb1d8c6…28effa
Audit this contract →
← previous block·next block →recent activity