← previous blocknext block →recent activity
Analyzing
Block #106,373,435
14 transactions · 14 stateful · 2026-09-20 04:56:29 UTC
Parallelism
57/100
Blocked
36%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,373,435 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w29w310w012w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x364036f4…10de
0x34b655…2a6f
12 touches
15 conflicts
0xac0b4a08…faae
0x34b655…2a6f
10 touches
10 conflicts
0xc9a6e112…69cc
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x89eaf36a…4e48
0x34b655…2a6f
4 touches
1 conflict
0x1afc902d…3ee1
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
15 conflicts on slot 0x364036f4f7…0110de
Audit this contract →
← previous block·next block →recent activity