← previous blocknext block →recent activity
Analyzing
Block #108,397,054
17 transactions · 16 stateful · 2026-09-27 06:45:06 UTC
Parallelism
59/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,397,054 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w411w513w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac105936…3323
0x34b655…2a6f
8 touches
6 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
8 touches
6 conflicts
0xc1da8f73…484c
0x34b655…2a6f
8 touches
6 conflicts
0x94e7f277…471b
0x34b655…2a6f
6 touches
3 conflicts
0xaba4ea7e…eea4
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x5900e8aa…2391
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 0xac105936b5…233323
Audit this contract →
← previous block·next block →recent activity