← previous blocknext block →recent activity
Analyzing
Block #108,566,101
23 transactions · 21 stateful · 2026-09-27 20:56:15 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,566,101 · 23 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
1w02w17w08w111w012w013w114w215w316w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xcb21158b…f18d
0x34b655…2a6f
10 touches
10 conflicts
0xe63c6702…03f3
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x28e2f7c3…e848
0x34b655…2a6f
8 touches
6 conflicts
0x31d88d27…7617
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xd25997d0…a689
0x1b6862…e19c
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
10 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity