← previous blocknext block →recent activity
Analyzing
Block #106,535,300
25 transactions · 23 stateful · 2026-09-20 18:31:10 UTC
Parallelism
64/100
Blocked
70%
Avg conflicts / tx
2.08
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,535,300 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w48w211w312w413w414w515w616w717w820w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fc536fb…1aa1
0x34b655…2a6f
18 touches
36 conflicts
0x93b5266f…c9d1
0x34b655…2a6f
14 touches
21 conflicts
0x809e6727…f36d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe283e878…7262
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa35509fa…5cb3
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
36 conflicts on slot 0x0fc536fb1f…c81aa1
Audit this contract →
← previous block·next block →recent activity