← previous blocknext block →recent activity
Analyzing
Block #105,542,293
23 transactions · 20 stateful · 2026-09-17 07:10:52 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,542,293 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w07w19w111w013w115w116w118w219w321w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e9210b8…64ae
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
6 touches
3 conflicts
0x18978822…2623
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x43ca04fd…f4a3
0x34b655…2a6f
4 touches
1 conflict
0x615bc8cc…15d2
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
6 conflicts on slot 0x0e9210b8b0…6c64ae
Audit this contract →
← previous block·next block →recent activity