← previous blocknext block →recent activity
Analyzing
Block #101,924,187
21 transactions · 17 stateful · 2026-09-04 14:27:21 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,924,187 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w28w19w215w216w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa62eb46f…89b1
0x34b655…2a6f
6 touches
3 conflicts
0xa7e3ddfa…f0c7
0x34b655…2a6f
6 touches
3 conflicts
0x56e0d685…c960
0x34b655…2a6f
6 touches
3 conflicts
0xc853be2d…b18f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x6c7c1a4b…5751
0x34b655…2a6f
6 touches
3 conflicts
0xfcd7574f…a3a2
0x34b655…2a6f
6 touches
3 conflicts
0xeb1b66a1…ce4e
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
3 conflicts on slot 0xa62eb46fdf…0289b1
Audit this contract →
← previous block·next block →recent activity