← previous blocknext block →recent activity
Analyzing
Block #108,567,932
23 transactions · 20 stateful · 2026-09-27 21:05:27 UTC
Parallelism
87/100
Blocked
35%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,567,932 · 23 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
4w05w16w08w09w110w111w012w113w114w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf4b5f6f…49cc
0x34b655…2a6f
6 touches
3 conflicts
0xed8224d3…528e
0x34b655…2a6f
4 touches
1 conflict
0x532af68d…503d
0x34b655…2a6f
4 touches
1 conflict
0xaf6eaf2e…f499
0x34b655…2a6f
4 touches
1 conflict
0xc2fe6ed6…f8be
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0xaf4b5f6fbd…2c49cc
Audit this contract →
← previous block·next block →recent activity