← previous blocknext block →recent activity
Analyzing
Block #108,641,821
19 transactions · 18 stateful · 2026-09-28 03:17:30 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,641,821 · 19 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
1w02w13w25w06w17w112w113w214w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d87891f…4552
0x34b655…2a6f
8 touches
6 conflicts
0xdacb24f7…56ce
0x34b655…2a6f
8 touches
6 conflicts
0xd5a25205…645e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xcb21158b…f18d
0x34b655…2a6f
6 touches
3 conflicts
0x0e915bda…62e7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xa8af951f…0d96
0xd32edf…ff58
5 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 0x2d87891f1a…d64552
Audit this contract →
← previous block·next block →recent activity