← previous blocknext block →recent activity
Analyzing
Block #101,661,422
30 transactions · 26 stateful · 2026-09-03 16:24:18 UTC
Parallelism
87/100
Blocked
27%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,661,422 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w211w013w114w215w320w028w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a429191…9cda
0x34b655…2a6f
8 touches
6 conflicts
0xf36124ad…c08f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
6 touches
3 conflicts
0x642dcd46…cb2e
0x34b655…2a6f
6 touches
3 conflicts
0x67c1f465…38b3
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
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 0x3a42919159…6b9cda
Audit this contract →
← previous block·next block →recent activity