← previous blocknext block →recent activity
Analyzing
Block #93,135,219
12 transactions · 12 stateful · 2026-08-04 18:43:30 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,135,219 · 12 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
5w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf19c45c…d1a9
0x34b655…2a6f
4 touches
1 conflict
0xd8bc53a3…c2fe
0x34b655…2a6f
4 touches
1 conflict
0xaf19c45c…d1a8
0x34b655…2a6f
4 touches
1 conflict
0x039f1f6c…3155
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2b2eb14e…6dec
0x34b655…2a6f
3 touches
1 conflict
0x369a943e…aef6
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 0xaf19c45c22…9ed1a9
Audit this contract →
← previous block·next block →recent activity