← previous blocknext block →recent activity
Analyzing
Block #102,190,157
20 transactions · 18 stateful · 2026-09-05 12:55:49 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,190,157 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w18w19w114w015w116w219w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49509e76…cd79
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xa366dc41…b2d8
0xa6afd3…d132
6 touches
3 conflicts
0x71fad9ce…c11f
0x34b655…2a6f
6 touches
3 conflicts
0xba5743c7…21c5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0x49509e76f8…89cd79
Audit this contract →
← previous block·next block →recent activity