← previous blocknext block →recent activity
Analyzing
Block #101,299,393
14 transactions · 13 stateful · 2026-09-02 10:02:48 UTC
Parallelism
79/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,299,393 · 14 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
1w02w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33ce2799…dfd1
0x34b655…2a6f
4 touches
1 conflict
0xd5030b4f…d93b
0x34b655…2a6f
4 touches
1 conflict
0x676207a8…5d7e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x1fe70bb4…3140
0x34b655…2a6f
2 touches
0 conflicts
0x32287d4a…6699
0x34b655…2a6f
2 touches
0 conflicts
0x3d6c26e5…1b45
0x34b655…2a6f
2 touches
0 conflicts
0x521d27af…460a
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
1 conflict on slot 0x33ce27999c…6bdfd1
Audit this contract →
← previous block·next block →recent activity