← previous blocknext block →recent activity
Analyzing
Block #106,253,514
27 transactions · 24 stateful · 2026-09-19 18:53:01 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,253,514 · 27 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
2w04w05w16w27w38w011w112w013w014w116w222w023w224w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4aa0d940…cdac
0x34b655…2a6f
8 touches
6 conflicts
0xfccf4b5b…66ca
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x38c6ff01…689f
0x34b655…2a6f
6 touches
3 conflicts
0x5906754f…b584
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
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 0x4aa0d940d0…c5cdac
Audit this contract →
← previous block·next block →recent activity