← previous blocknext block →recent activity
Analyzing
Block #102,221,651
23 transactions · 23 stateful · 2026-09-05 15:35:15 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,221,651 · 23 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
1w02w15w09w110w211w012w113w214w316w317w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d470190…0880
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x6131316b…35d3
0x34b655…2a6f
6 touches
3 conflicts
0x1234432e…9626
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x786d66ce…ae70
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x2d47019007…470880
Audit this contract →
← previous block·next block →recent activity