← previous blocknext block →recent activity
Analyzing
Block #93,663,340
11 transactions · 10 stateful · 2026-08-06 14:58:42 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,663,340 · 11 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
2w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc351d6d…256b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x185eacc9…9e18
0x34b655…2a6f
2 touches
0 conflicts
0x1e2b2634…63f5
0x34b655…2a6f
2 touches
0 conflicts
0x1ed399c3…46f1
0x34b655…2a6f
2 touches
0 conflicts
0x31519d10…f76b
0x34b655…2a6f
2 touches
0 conflicts
0x378d61e4…7f15
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 0xcc351d6dd2…b1256b
Audit this contract →
← previous block·next block →recent activity