← previous blocknext block →recent activity
Analyzing
Block #108,482,538
21 transactions · 16 stateful · 2026-09-27 13:55:22 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,482,538 · 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
5w06w18w210w312w418w119w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cb2ad15…0483
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
8 touches
6 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
6 touches
3 conflicts
0x7006165a…df17
0x34b655…2a6f
6 touches
3 conflicts
0x9cc386e7…5d4d
0x34b655…2a6f
6 touches
3 conflicts
0x9daafdf9…bb53
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
6 conflicts on slot 0x5cb2ad1503…770483
Audit this contract →
← previous block·next block →recent activity