← previous blocknext block →recent activity
Analyzing
Block #108,642,481
18 transactions · 18 stateful · 2026-09-28 03:20:50 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,642,481 · 18 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
5w06w110w011w114w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a663e9a…a9ce
0x508254…98bd
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x859134b8…7920
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x05006bd2…56d1
0x508254…98bd
4 touches
1 conflict
0x05006bd2…56ea
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c4
0x508254…98bd
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: 0x508254c8…4a98bd
3 conflicts on slot 0x3a663e9a3a…2fa9ce
Audit this contract →
← previous block·next block →recent activity