← previous blocknext block →recent activity
Analyzing
Block #108,360,632
16 transactions · 14 stateful · 2026-09-27 03:41:50 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,360,632 · 16 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
1w02w15w010w111w212w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2768f3e8…fe70
0x34b655…2a6f
6 touches
3 conflicts
0x1ad8153e…06bf
0x34b655…2a6f
4 touches
1 conflict
0xe7869756…91af
0x34b655…2a6f
4 touches
1 conflict
0x1ce796f6…cbba
0x34b655…2a6f
4 touches
1 conflict
0xefc465f2…88c5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x248359b8…98ed
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 0x2768f3e840…03fe70
Audit this contract →
← previous block·next block →recent activity