← previous blocknext block →recent activity
Analyzing
Block #91,096,529
16 transactions · 14 stateful · 2026-07-28 15:43:34 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,096,529 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w09w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8563e3a…3f5b
0x7b9256…1fb2
4 touches
1 conflict
0x8c500c4b…788a
0x7b9256…1fb2
4 touches
1 conflict
0x8c500c4b…788d
0x7b9256…1fb2
4 touches
1 conflict
0xa8563e3a…3f59
0x7b9256…1fb2
4 touches
1 conflict
0xa8563e3a…3f5a
0x7b9256…1fb2
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x4d5053d1…3b7d
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: 0x7b9256fd…e21fb2
1 conflict on slot 0xa8563e3a53…ca3f5b
Audit this contract →
← previous block·next block →recent activity