← previous blocknext block →recent activity
Analyzing
Block #93,537,476
9 transactions · 7 stateful · 2026-08-06 04:25:58 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,537,476 · 9 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
2w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x76f00b05…2407
0x34b655…2a6f
3 touches
1 conflict
0xfb206df0…fd21
0x34b655…2a6f
3 touches
1 conflict
0x36a76bd2…1fb0
0x34b655…2a6f
2 touches
0 conflicts
0x48db007d…d769
0x34b655…2a6f
2 touches
0 conflicts
0x62dee602…2b2c
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 0x4e8c4408ae…50d37b
Audit this contract →
← previous block·next block →recent activity