← previous blocknext block →recent activity
Analyzing
Block #90,823,397
16 transactions · 15 stateful · 2026-07-27 16:48:35 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
0.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,823,397 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w27w28w311w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbabe821d…939b
0x34b655…2a6f
6 touches
3 conflicts
0x9ae859db…2d84
0x34b655…2a6f
6 touches
3 conflicts
0x2267f8c4…a571
0x34b655…2a6f
6 touches
3 conflicts
0xa49f611d…acb1
0x34b655…2a6f
6 touches
3 conflicts
0x26d1c221…4d2a
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity