← previous blocknext block →recent activity
Analyzing
Block #102,098,202
15 transactions · 14 stateful · 2026-09-05 05:09:41 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,098,202 · 15 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
1w02w13w04w15w010w113w014w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68531239…e9a3
0x34b655…2a6f
6 touches
3 conflicts
0x46356904…5ead
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x6762cac2…3fb0
0x34b655…2a6f
2 touches
0 conflicts
0x75c5164b…3b3e
0x34b655…2a6f
2 touches
0 conflicts
0x817653c6…9d90
0x34b655…2a6f
2 touches
0 conflicts
0xa9bc0c61…108a
0x34b655…2a6f
2 touches
0 conflicts
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 0x68531239f9…5ae9a3
Audit this contract →
← previous block·next block →recent activity