← previous blocknext block →recent activity
Analyzing
Block #102,010,407
42 transactions · 35 stateful · 2026-09-04 21:44:44 UTC
Parallelism
67/100
Blocked
66%
Avg conflicts / tx
2.81
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #102,010,407 · 42 txs across 14 waves · depth 14
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
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w29w310w412w513w614w715w816w917w1018w1119w1220w1328w129w235w339w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
28 touches
91 conflicts
0x00500a94…20d5
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe108b282…58b3
0x34b655…2a6f
6 touches
3 conflicts
0x41c56387…a8f6
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: 0xf5b5f7f8…a36d70
91 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity