← previous blocknext block →recent activity
Analyzing
Block #90,794,425
25 transactions · 22 stateful · 2026-07-27 14:22:44 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,794,425 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w08w110w213w114w217w018w321w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x1ef09fe8…c548
0x34b655…2a6f
4 touches
1 conflict
0x24eaf46d…8c2e
0x34b655…2a6f
4 touches
1 conflict
0x2f358e74…1022
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x3b1ce1dd…dc2f
0x34b655…2a6f
4 touches
1 conflict
0x58750d82…7315
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity