← previous blocknext block →recent activity
Analyzing
Block #102,530,324
35 transactions · 27 stateful · 2026-09-06 17:39:35 UTC
Parallelism
89/100
Blocked
44%
Avg conflicts / tx
0.66
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,530,324 · 35 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
1w03w04w15w07w18w213w014w017w018w121w122w123w324w225w027w129w230w031w134w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0xd8aeb9dc…6839
0xd32edf…ff58
7 touches
6 conflicts
0xe108b282…58b3
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4559d99a…3138
0x34b655…2a6f
4 touches
1 conflict
0x939cdd56…00c8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity