← previous blocknext block →recent activity
Analyzing
Block #102,524,631
29 transactions · 25 stateful · 2026-09-06 17:10:42 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,524,631 · 29 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
5w06w19w010w111w012w014w116w218w324w425w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77352fc8…a595
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xdb8288e3…7979
0x34b655…2a6f
6 touches
3 conflicts
0xe7ad475a…0e41
0x34b655…2a6f
6 touches
3 conflicts
0x60a536a6…ef7a
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
3 conflicts on slot 0x77352fc8d4…e2a595
Audit this contract →
← previous block·next block →recent activity