← previous blocknext block →recent activity
Analyzing
Block #105,920,604
23 transactions · 21 stateful · 2026-09-18 14:57:17 UTC
Parallelism
70/100
Blocked
48%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,920,604 · 23 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
1w02w16w011w012w113w214w315w416w517w620w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0xe7702ef2…3e4b
0x34b655…2a6f
12 touches
15 conflicts
0x4089d428…b018
0x34b655…2a6f
12 touches
15 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
12 touches
15 conflicts
0x5e0b0448…2ab7
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf174cda6…19f3
0x34b655…2a6f
4 touches
1 conflict
0x20b1228b…2487
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity