← previous blocknext block →recent activity
Analyzing
Block #105,749,468
7 transactions · 7 stateful · 2026-09-18 00:33:40 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,749,468 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5847c4d…a65c
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5f34739b…14fd
0x34b655…2a6f
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
2 touches
0 conflicts
0x228502e4…0f65
0x34b655…2a6f
2 touches
0 conflicts
0x6b9d5894…02fa
0x34b655…2a6f
2 touches
0 conflicts
0xca841faa…486a
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xc5847c4d32…49a65c
Audit this contract →
← previous block·next block →recent activity