← previous blocknext block →recent activity
Analyzing
Block #108,113,548
16 transactions · 14 stateful · 2026-09-26 06:58:21 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,113,548 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w08w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8c7dc95…c784
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x507c6e76…4b4f
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
2 touches
0 conflicts
0x74b1a49f…f323
0x34b655…2a6f
2 touches
0 conflicts
0xd8485928…dcb4
0x34b655…2a6f
2 touches
0 conflicts
0x86fddbb2…c0e9
0x37db7f…ec7b
2 touches
0 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
1 conflict on slot 0xc8c7dc95a0…01c784
Audit this contract →
← previous block·next block →recent activity