← previous blocknext block →recent activity
Analyzing
Block #106,109,371
22 transactions · 17 stateful · 2026-09-19 06:47:28 UTC
Parallelism
77/100
Blocked
59%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,109,371 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w16w07w18w211w312w213w416w420w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ec0395a…d7ba
0x34b655…2a6f
8 touches
6 conflicts
0x735a86cd…b64d
0x34b655…2a6f
8 touches
6 conflicts
0xf91d37c7…39f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
0x961c0cd9…0937
0x34b655…2a6f
4 touches
1 conflict
0xbaf6ed88…c179
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
6 conflicts on slot 0x8ec0395a7b…09d7ba
Audit this contract →
← previous block·next block →recent activity