← previous blocknext block →recent activity
Analyzing
Block #90,784,050
31 transactions · 18 stateful · 2026-07-27 13:30:30 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,784,050 · 31 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
2w09w010w113w114w116w220w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xde9d38a8…4c0f
0x34b655…2a6f
6 touches
3 conflicts
0x4d7e366b…7690
0x34b655…2a6f
4 touches
1 conflict
0x5f7b9c22…6abb
0x34b655…2a6f
4 touches
1 conflict
0x65f01a9c…34e0
0x34b655…2a6f
4 touches
1 conflict
0x6719a767…9d62
0x34b655…2a6f
4 touches
1 conflict
0x841e8727…0e8c
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 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity