← previous blocknext block →recent activity
Analyzing
Block #106,109,250
14 transactions · 13 stateful · 2026-09-19 06:46:52 UTC
Parallelism
57/100
Blocked
54%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,109,250 · 14 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
1w02w14w05w16w07w18w09w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94a8f845…0e2f
0x34b655…2a6f
10 touches
10 conflicts
0xa03c2a35…52e6
0x34b655…2a6f
6 touches
3 conflicts
0x26867cdc…dab5
0x34b655…2a6f
6 touches
3 conflicts
0x961c0cd9…0937
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x5a3732cb…edb1
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0dd3d3cd…7281
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 0x94a8f845c6…200e2f
Audit this contract →
← previous block·next block →recent activity