← previous blocknext block →recent activity
Analyzing
Block #108,515,428
23 transactions · 22 stateful · 2026-09-27 16:40:58 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,515,428 · 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
1w04w15w06w08w110w011w114w116w117w218w219w322w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x532af68d…503d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
6 touches
3 conflicts
0xaf28de86…7e09
0xd32edf…ff58
5 touches
3 conflicts
0x132b9de1…183b
0x34b655…2a6f
4 touches
1 conflict
0x1ad8153e…06bf
0x34b655…2a6f
4 touches
1 conflict
0x2735f8ea…3ce2
0x34b655…2a6f
4 touches
1 conflict
0x2cc51b34…c5a8
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
3 conflicts on slot 0x532af68dd4…b5503d
Audit this contract →
← previous block·next block →recent activity