← previous blocknext block →recent activity
Analyzing
Block #102,525,082
32 transactions · 27 stateful · 2026-09-06 17:13:02 UTC
Parallelism
84/100
Blocked
30%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,525,082 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w111w112w213w327w028w129w230w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3222147c…8d93
0x34b655…2a6f
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x690abd67…571e
0x34b655…2a6f
4 touches
1 conflict
0x100812e9…12b7
0x34b655…2a6f
4 touches
1 conflict
0x803fe3bc…be74
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: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity