← previous blocknext block →recent activity
Analyzing
Block #108,360,313
22 transactions · 20 stateful · 2026-09-27 03:40:13 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,360,313 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w111w012w114w215w316w417w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
16 touches
28 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
16 touches
28 conflicts
0xa69bb4e1…f2bb
0x34b655…2a6f
6 touches
3 conflicts
0xc2fe6ed6…f8be
0x34b655…2a6f
6 touches
3 conflicts
0x1f84ce8a…5acc
0x34b655…2a6f
6 touches
3 conflicts
0x17bbe4f8…08c5
0xe52b14…7230
4 touches
1 conflict
0x3cebc8f1…975c
0xe52b14…7230
4 touches
1 conflict
0x58733c38…f2cd
0xe52b14…7230
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
28 conflicts on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity