← previous blocknext block →recent activity
Analyzing
Block #105,620,139
40 transactions · 32 stateful · 2026-09-17 13:42:43 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,620,139 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w38w49w510w611w727w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e8f1bea…875b
0x34b655…2a6f
16 touches
28 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
10 touches
10 conflicts
0x10a5a231…be40
0x34b655…2a6f
10 touches
10 conflicts
0x9eef1610…1564
0x34b655…2a6f
8 touches
6 conflicts
0x0f04fb6a…83e0
0x34b655…2a6f
8 touches
6 conflicts
0x0fcb1428…3534
0x34b655…2a6f
8 touches
6 conflicts
0x2b3a3743…b14a
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
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
28 conflicts on slot 0x5e8f1bea2a…0d875b
Audit this contract →
← previous block·next block →recent activity