← previous blocknext block →recent activity
Analyzing
Block #93,555,181
14 transactions · 12 stateful · 2026-08-06 05:54:58 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,555,181 · 14 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
4w05w16w07w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e56f6b6…5940
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x12bc2c56…0d74
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
2 touches
0 conflicts
0x513bcef5…048e
0x01bff4…1071
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x40970e69…da50
0x2b46c0…1669
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 0x1e56f6b6e1…615940
Audit this contract →
← previous block·next block →recent activity