← previous blocknext block →recent activity
Analyzing
Block #101,956,523
17 transactions · 14 stateful · 2026-09-04 17:11:27 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,956,523 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w010w111w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8590b692…b267
0x34b655…2a6f
4 touches
1 conflict
0xbf08f662…f943
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x27c8497b…dcc4
0x754704…b603
4 touches
1 conflict
0x87c3dfca…7ce9
0x754704…b603
4 touches
1 conflict
0xbb95fb3e…c47b
0x754704…b603
4 touches
1 conflict
0x1a489fe9…adcd
0x99c7a7…8bf0
4 touches
1 conflict
0xc48bb6d2…c376
0x99c7a7…8bf0
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
1 conflict on slot 0x8590b69238…6ab267
Audit this contract →
← previous block·next block →recent activity