← previous blocknext block →recent activity
Analyzing
Block #101,854,263
21 transactions · 19 stateful · 2026-09-04 08:34:16 UTC
Parallelism
81/100
Blocked
53%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,854,263 · 21 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
2w03w14w05w06w17w28w112w013w114w116w217w318w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a7af3fd…72a6
0x34b655…2a6f
6 touches
3 conflicts
0x809f2ba8…89d3
0x34b655…2a6f
6 touches
3 conflicts
0xc014c511…ac0e
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xc3483764…f29d
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x03da5c00…b353
0x34b655…2a6f
4 touches
1 conflict
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 0x8a7af3fdbb…2b72a6
Audit this contract →
← previous block·next block →recent activity