← previous blocknext block →recent activity
Analyzing
Block #108,605,421
24 transactions · 21 stateful · 2026-09-28 00:14:09 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,605,421 · 24 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
1w03w011w112w115w016w118w119w220w321w022w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cb7ee74…b8a5
0x34b655…2a6f
8 touches
6 conflicts
0x3aa20582…a475
0x34b655…2a6f
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x5900e8aa…2391
0x34b655…2a6f
4 touches
1 conflict
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xf275b4ca…57b8
0xe52b14…7230
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 0x3cb7ee74c7…7db8a5
Audit this contract →
← previous block·next block →recent activity