← previous blocknext block →recent activity
Analyzing
Block #103,216,335
37 transactions · 34 stateful · 2026-09-09 03:20:25 UTC
Parallelism
89/100
Blocked
35%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,216,335 · 37 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w29w010w113w022w023w024w126w227w129w331w333w034w135w236w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
6 touches
3 conflicts
0x65e6e603…cb44
0x34b655…2a6f
6 touches
3 conflicts
0x65e6e603…cb45
0x34b655…2a6f
6 touches
3 conflicts
0x6956d31b…6393
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity