← previous blocknext block →recent activity
Analyzing
Block #107,812,952
29 transactions · 20 stateful · 2026-09-25 05:45:25 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,812,952 · 29 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
2w03w112w013w015w116w217w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xe2995197…337c
0x860869…ff01
4 touches
1 conflict
0x740fff9f…4244
0x34b655…2a6f
4 touches
1 conflict
0xa6b55494…76c2
0x34b655…2a6f
4 touches
1 conflict
0xcc73f55f…fff2
0x34b655…2a6f
4 touches
1 conflict
0xe98ab6b4…80ee
0x34b655…2a6f
4 touches
1 conflict
0xebecb62b…33eb
0x34b655…2a6f
4 touches
1 conflict
0xf15273a1…2c52
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity