← previous blocknext block →recent activity
Analyzing
Block #108,336,060
26 transactions · 26 stateful · 2026-09-27 01:38:10 UTC
Parallelism
69/100
Blocked
62%
Avg conflicts / tx
2.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,336,060 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w27w08w09w110w211w312w414w516w518w320w422w623w724w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
14 touches
21 conflicts
0x451e482b…7e7d
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
12 touches
15 conflicts
0x3dc09507…c195
0x34b655…2a6f
10 touches
10 conflicts
0xa3ff1ab2…8ae3
0x34b655…2a6f
10 touches
10 conflicts
0xbd24b5a5…4efa
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 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
21 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity