← previous blocknext block →recent activity
Analyzing
Block #108,549,946
26 transactions · 22 stateful · 2026-09-27 19:34:43 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,549,946 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w38w411w512w113w214w215w316w420w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c26d635…1bbf
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0xf625f91c…3abe
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x9b334941…fddf
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x49890ced…6f23
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 0x6c26d63540…461bbf
Audit this contract →
← previous block·next block →recent activity