← previous blocknext block →recent activity
Analyzing
Block #102,817,705
13 transactions · 13 stateful · 2026-09-07 17:52:12 UTC
Parallelism
54/100
Blocked
46%
Avg conflicts / tx
1.23
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,817,705 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w28w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb42455cc…4e5a
0x40c49f…2af0
12 touches
15 conflicts
0x002fed35…79fa
0x2a68ba…90c5
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x3040553c…5e28
0x754704…b603
2 touches
0 conflicts
0x3d9eb674…b3fb
0x754704…b603
2 touches
0 conflicts
0x4c1fbdf6…953d
0x754704…b603
2 touches
0 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: 0x40c49f17…d22af0
15 conflicts on slot 0xb42455ccd8…4b4e5a
Audit this contract →
← previous block·next block →recent activity