← previous blocknext block →recent activity
Analyzing
Block #103,221,585
22 transactions · 19 stateful · 2026-09-09 03:46:52 UTC
Parallelism
55/100
Blocked
58%
Avg conflicts / tx
2.05
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #103,221,585 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w211w213w314w416w418w619w720w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
16 touches
28 conflicts
0x7aad02c6…b979
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
8 touches
6 conflicts
0x8a377bad…474b
0x34b655…2a6f
6 touches
5 conflicts
0x55e05c7a…0ab5
0x34b655…2a6f
6 touches
3 conflicts
0x587dcf2c…7759
0x34b655…2a6f
6 touches
3 conflicts
0x58b27dde…52d1
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
28 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity