← previous blocknext block →recent activity
Analyzing
Block #106,241,914
17 transactions · 17 stateful · 2026-09-19 17:54:38 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,241,914 · 17 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
2w03w14w25w38w09w113w415w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe43b345e…a4e3
0x34b655…2a6f
10 touches
10 conflicts
0xc48f270a…c635
0x34b655…2a6f
8 touches
6 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
6 touches
3 conflicts
0xb9b077a8…e029
0x34b655…2a6f
6 touches
3 conflicts
0xff2ce193…156b
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
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
10 conflicts on slot 0xe43b345e79…6aa4e3
Audit this contract →
← previous block·next block →recent activity