← previous blocknext block →recent activity
Analyzing
Block #108,468,560
21 transactions · 19 stateful · 2026-09-27 12:45:01 UTC
Parallelism
71/100
Blocked
58%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,468,560 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w27w310w011w112w213w314w417w518w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20492d53…80f9
0x34b655…2a6f
12 touches
15 conflicts
0x71111d36…6b94
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0xee835f9e…e16a
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x20492d531d…7380f9
Audit this contract →
← previous block·next block →recent activity