← previous blocknext block →recent activity
Analyzing
Block #108,446,669
18 transactions · 13 stateful · 2026-09-27 10:54:49 UTC
Parallelism
83/100
Blocked
23%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,446,669 · 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
4w012w014w116w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03f699e7…537e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xcb45d9d6…cb83
0x1b6862…e19c
4 touches
1 conflict
0xc0e38099…d3cb
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
2 touches
0 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
3 conflicts on slot 0x03f699e788…b8537e
Audit this contract →
← previous block·next block →recent activity