← previous blocknext block →recent activity
Analyzing
Block #108,102,763
18 transactions · 16 stateful · 2026-09-26 06:04:04 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,102,763 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w09w010w111w112w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85d24b5f…92b7
0x34b655…2a6f
4 touches
1 conflict
0x908b3417…88d2
0x34b655…2a6f
4 touches
1 conflict
0x970da48a…345b
0x34b655…2a6f
4 touches
1 conflict
0xc90f5dcb…ebee
0x34b655…2a6f
4 touches
1 conflict
0xd33a3d56…2ae3
0x34b655…2a6f
4 touches
1 conflict
0xdced4209…6afa
0x34b655…2a6f
4 touches
1 conflict
0xf7063105…100b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
1 conflict on slot 0x85d24b5fa8…7692b7
Audit this contract →
← previous block·next block →recent activity