← previous blocknext block →recent activity
Analyzing
Block #101,248,094
20 transactions · 20 stateful · 2026-09-02 05:44:42 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,248,094 · 20 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
3w04w05w16w29w010w311w113w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe97d54c5…ef6f
0x34b655…2a6f
8 touches
6 conflicts
0xca17206e…985f
0x34b655…2a6f
6 touches
3 conflicts
0x5ce08c09…7f3e
0xa6afd3…d132
4 touches
1 conflict
0x64e296b0…cd76
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb534edae…31fa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf039e2f8…3d8a
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 0xe97d54c5c1…33ef6f
Audit this contract →
← previous block·next block →recent activity