← previous blocknext block →recent activity
Analyzing
Block #108,501,682
24 transactions · 24 stateful · 2026-09-27 15:31:47 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
1.04
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,501,682 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w17w29w315w116w217w318w419w020w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
8 touches
6 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x74851f5e…fadd
0x34b655…2a6f
6 touches
3 conflicts
0xdabae01b…82be
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xe8058ec4…ebac
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 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity