← previous blocknext block →recent activity
Analyzing
Block #90,791,395
14 transactions · 12 stateful · 2026-07-27 14:07:29 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,791,395 · 14 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
4w05w06w19w110w212w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x917f99a5…7989
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0x6aa0302c…bc76
0x34b655…2a6f
4 touches
1 conflict
0x78b60ad8…8468
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0xab13117b…e40e
0x34b655…2a6f
4 touches
1 conflict
0xb506a4b2…9041
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 0x917f99a53e…3d7989
Audit this contract →
← previous block·next block →recent activity