← previous blocknext block →recent activity
Analyzing
Block #106,189,092
24 transactions · 22 stateful · 2026-09-19 13:28:41 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,189,092 · 24 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
5w06w110w211w312w413w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36eb9d19…32f7
0x34b655…2a6f
14 touches
21 conflicts
0xac0b4a08…faae
0x34b655…2a6f
10 touches
10 conflicts
0x6b267bdf…b173
0x34b655…2a6f
6 touches
3 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x67a56c8b…f955
0x34b655…2a6f
6 touches
3 conflicts
0x854ce402…932a
0x34b655…2a6f
4 touches
1 conflict
0x9eef1610…1564
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x36eb9d1999…be32f7
Audit this contract →
← previous block·next block →recent activity