← previous blocknext block →recent activity
Analyzing
Block #102,316,812
31 transactions · 23 stateful · 2026-09-05 23:37:34 UTC
Parallelism
87/100
Blocked
30%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,316,812 · 31 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
1w04w15w28w09w011w012w119w325w329w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x839c0c71…bada
0x34b655…2a6f
8 touches
6 conflicts
0x94dabb65…43a3
0x34b655…2a6f
6 touches
3 conflicts
0x347abf57…4b86
0x34b655…2a6f
4 touches
1 conflict
0x3643741b…109c
0x34b655…2a6f
4 touches
1 conflict
0x36a2423d…e290
0x34b655…2a6f
4 touches
1 conflict
0x45885570…ed97
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
6 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity