← previous blocknext block →recent activity
Analyzing
Block #102,409,237
39 transactions · 35 stateful · 2026-09-06 07:25:47 UTC
Parallelism
69/100
Blocked
63%
Avg conflicts / tx
2.49
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #102,409,237 · 39 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w06w17w08w09w110w211w013w114w015w118w019w223w225w326w428w129w232w534w735w837w1038w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x5b09bf44…5907
0xa6afd3…d132
8 touches
6 conflicts
0x70d81211…f49f
0x34b655…2a6f
8 touches
6 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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity