← previous blocknext block →recent activity
Analyzing
Block #91,547,195
12 transactions · 12 stateful · 2026-07-30 05:33:05 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,547,195 · 12 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
1w03w04w15w06w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52b477bc…7ccf
0x34b655…2a6f
8 touches
6 conflicts
0xcc58c80b…ff79
0x34b655…2a6f
6 touches
3 conflicts
0x0b1a9431…183e
0x34b655…2a6f
4 touches
1 conflict
0x406b6576…1a33
0x34b655…2a6f
4 touches
1 conflict
0xfc5ab308…f714
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc8abf84c…9ea9
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 0x52b477bcb8…5d7ccf
Audit this contract →
← previous block·next block →recent activity