← previous blocknext block →recent activity
Analyzing
Block #106,786,400
23 transactions · 20 stateful · 2026-09-21 15:35:55 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,786,400 · 23 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
1w02w110w011w112w015w216w317w420w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bd4088b…62b9
0x34b655…2a6f
8 touches
6 conflicts
0x46cc3372…2fee
0x34b655…2a6f
8 touches
6 conflicts
0x4be9812b…48a9
0x34b655…2a6f
6 touches
3 conflicts
0x8a02d049…f481
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa86cc3f9…9d91
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
6 conflicts on slot 0x6bd4088b4e…5a62b9
Audit this contract →
← previous block·next block →recent activity