← previous blocknext block →recent activity
Analyzing
Block #108,439,011
27 transactions · 25 stateful · 2026-09-27 10:16:16 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,439,011 · 27 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
2w06w18w010w111w013w114w215w016w117w320w021w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbaa140e0…027d
0x34b655…2a6f
6 touches
3 conflicts
0xf35dca9e…bd8b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x7d82a6c8…5faf
0x34b655…2a6f
6 touches
3 conflicts
0x9717c01a…51f0
0xd32edf…ff58
5 touches
3 conflicts
0x6a230536…82e5
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 0xbaa140e025…53027d
Audit this contract →
← previous block·next block →recent activity