← previous blocknext block →recent activity
Analyzing
Block #91,548,432
14 transactions · 10 stateful · 2026-07-30 05:39:18 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,548,432 · 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
4w05w17w18w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b56f79b…310f
0x34b655…2a6f
4 touches
1 conflict
0x521a91b0…b4c9
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xb193c4fa…4abd
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcc58c80b…ff79
0x34b655…2a6f
4 touches
1 conflict
0x21280422…0930
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
1 conflict on slot 0x3b56f79b81…31310f
Audit this contract →
← previous block·next block →recent activity