← previous blocknext block →recent activity
Analyzing
Block #93,677,144
17 transactions · 16 stateful · 2026-08-06 16:08:06 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,677,144 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w29w310w114w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ba6ae4a…90cb
0x34b655…2a6f
8 touches
6 conflicts
0x310afe2c…83e1
0x34b655…2a6f
8 touches
6 conflicts
0xd676e291…3ecf
0x34b655…2a6f
6 touches
3 conflicts
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0x29a2aad6…286b
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x353a3a00…5e0a
0x34b655…2a6f
4 touches
1 conflict
0x3610cfd5…236a
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
6 conflicts on slot 0x9ba6ae4a28…c990cb
Audit this contract →
← previous block·next block →recent activity