← previous blocknext block →recent activity
Analyzing
Block #90,793,619
15 transactions · 14 stateful · 2026-07-27 14:18:41 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,793,619 · 15 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
2w03w17w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8289a4c2…920c
0x34b655…2a6f
4 touches
1 conflict
0x62dbeb4d…a388
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xb1c67a7d…b9b1
0x34b655…2a6f
4 touches
1 conflict
0x2f29153d…cae9
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0x7fb3faa1…2dbd
0x34b655…2a6f
4 touches
1 conflict
0x51e3d69f…56db
0x34b655…2a6f
2 touches
0 conflicts
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 0x8289a4c286…07920c
Audit this contract →
← previous block·next block →recent activity