← previous blocknext block →recent activity
Analyzing
Block #93,656,138
21 transactions · 20 stateful · 2026-08-06 14:22:30 UTC
Parallelism
76/100
Blocked
45%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,656,138 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w16w07w08w19w210w313w115w316w119w020w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x681cc0ee…eb83
0x34b655…2a6f
6 touches
3 conflicts
0x1ad72688…0c1f
0x34b655…2a6f
4 touches
1 conflict
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x2c390858…b1ed
0x34b655…2a6f
4 touches
1 conflict
0x323c81b3…7850
0x34b655…2a6f
4 touches
1 conflict
0x3e5604c0…8bc3
0x34b655…2a6f
4 touches
1 conflict
0x41f1e2e5…2edf
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
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 0x681cc0ee41…87eb83
Audit this contract →
← previous block·next block →recent activity