← previous blocknext block →recent activity
Analyzing
Block #90,804,306
31 transactions · 22 stateful · 2026-07-27 15:12:27 UTC
Parallelism
81/100
Blocked
55%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,804,306 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w116w017w118w219w220w321w122w323w424w225w328w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41377979…0a18
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
0xa3f6f7c8…2436
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbadc08dd…cf76
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
10 conflicts on slot 0x413779793d…8f0a18
Audit this contract →
← previous block·next block →recent activity