← previous blocknext block →recent activity
Analyzing
Block #108,575,264
22 transactions · 21 stateful · 2026-09-27 21:42:21 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,575,264 · 22 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
4w05w17w09w112w013w114w015w216w317w118w420w521w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e84bea1…20bc
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3da6ec2b…b836
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x39d701b3…ab59
0x34b655…2a6f
4 touches
1 conflict
0x43518af2…6940
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
6 conflicts on slot 0x2e84bea1b0…ca20bc
Audit this contract →
← previous block·next block →recent activity