← previous blocknext block →recent activity
Analyzing
Block #108,997,182
21 transactions · 15 stateful · 2026-09-29 09:11:15 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,997,182 · 21 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
1w04w05w17w08w19w010w111w012w213w317w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9a14f52…bd3f
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x31cea086…6d5e
0x34b655…2a6f
4 touches
1 conflict
0x41f69129…1c71
0x34b655…2a6f
4 touches
1 conflict
0x67cd2dce…6f0b
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 0xc9a14f5243…1dbd3f
Audit this contract →
← previous block·next block →recent activity