← previous blocknext block →recent activity
Analyzing
Block #103,987,714
71 transactions · 35 stateful · 2026-09-11 20:11:58 UTC
Parallelism
89/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #103,987,714 · 71 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
5w06w18w09w110w211w314w420w521w622w759w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xaad6be10…0801
0x2a68ba…90c5
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x21c55e43…e6d9
0xa6afd3…d132
8 touches
6 conflicts
0xb99a01e4…684f
0xa6afd3…d132
8 touches
6 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity