← previous blocknext block →recent activity
Analyzing
Block #108,103,454
33 transactions · 31 stateful · 2026-09-26 06:07:32 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,103,454 · 33 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w08w19w010w111w213w214w321w422w126w227w230w031w132w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74e485b1…d380
0x34b655…2a6f
8 touches
6 conflicts
0x75305aba…ba3a
0x34b655…2a6f
8 touches
6 conflicts
0x451e482b…7e7d
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x3643741b…109c
0x34b655…2a6f
6 touches
3 conflicts
0x3f152ba8…cea6
0x34b655…2a6f
6 touches
3 conflicts
0x454cdf57…aebc
0x34b655…2a6f
6 touches
3 conflicts
0x45885570…ed97
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 0x74e485b13a…f0d380
Audit this contract →
← previous block·next block →recent activity