← previous blocknext block →recent activity
Analyzing
Block #108,310,337
40 transactions · 34 stateful · 2026-09-26 23:28:44 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
1.55
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,310,337 · 40 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w112w013w114w215w318w219w323w424w430w431w534w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0019
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb81
0x1b6862…e19c
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xe5e7089a…fb91
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