← previous blocknext block →recent activity
Analyzing
Block #106,199,062
20 transactions · 20 stateful · 2026-09-19 14:18:51 UTC
Parallelism
65/100
Blocked
45%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,199,062 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w29w310w412w513w614w015w117w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x411b6473…3740
0x34b655…2a6f
12 touches
15 conflicts
0x5717771c…45ed
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xac0b4a08…faae
0x34b655…2a6f
4 touches
1 conflict
0xb550abea…2729
0x34b655…2a6f
4 touches
1 conflict
0xb92d5c2a…9c98
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 0x411b647303…d23740
Audit this contract →
← previous block·next block →recent activity