← previous blocknext block →recent activity
Analyzing
Block #106,917,280
22 transactions · 20 stateful · 2026-09-22 02:34:43 UTC
Parallelism
73/100
Blocked
35%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,917,280 · 22 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
1w05w06w18w09w110w211w312w413w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x251ee419…4404
0x34b655…2a6f
12 touches
15 conflicts
0x70986451…c6bd
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x35c68080…aace
0x851145…3f07
4 touches
1 conflict
0x7b7a477a…9155
0x851145…3f07
4 touches
1 conflict
0xc9327614…ba36
0x851145…3f07
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 0x251ee41913…494404
Audit this contract →
← previous block·next block →recent activity