← previous blocknext block →recent activity
Analyzing
Block #93,558,278
12 transactions · 11 stateful · 2026-08-06 06:10:32 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,558,278 · 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
1w02w13w04w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a46e23f…d28d
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x7a2c83a3…a29a
0x34b655…2a6f
4 touches
1 conflict
0x176686bb…97a5
0x34b655…2a6f
2 touches
0 conflicts
0x21d3d9b9…466c
0x34b655…2a6f
2 touches
0 conflicts
0x322fa8a2…7d2d
0x34b655…2a6f
2 touches
0 conflicts
0x342ec28c…cd7f
0x34b655…2a6f
2 touches
0 conflicts
0x36df2f54…1483
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 0x6a46e23fa7…c7d28d
Audit this contract →
← previous block·next block →recent activity