← previous blocknext block →recent activity
Analyzing
Block #106,435,583
21 transactions · 21 stateful · 2026-09-20 10:09:16 UTC
Parallelism
62/100
Blocked
48%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,435,583 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w07w112w213w314w415w516w517w618w720w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd563f3a1…94b1
0x34b655…2a6f
14 touches
21 conflicts
0xcabf7820…f115
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xdd77da90…6df4
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x5e2ea201…12de
0x34b655…2a6f
6 touches
3 conflicts
0x56e56687…1766
0x34b655…2a6f
4 touches
1 conflict
0x760fc6c3…71f9
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
21 conflicts on slot 0xd563f3a18c…f494b1
Audit this contract →
← previous block·next block →recent activity