← previous blocknext block →recent activity
Analyzing
Block #90,817,495
16 transactions · 14 stateful · 2026-07-27 16:18:53 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,817,495 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8667a2e…b5e2
0x34b655…2a6f
4 touches
1 conflict
0x94bb14fe…8f47
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x10a7d541…fc05
0x34b655…2a6f
2 touches
0 conflicts
0x1346ac01…31f2
0x34b655…2a6f
2 touches
0 conflicts
0x1ffbc5c9…461f
0x34b655…2a6f
2 touches
0 conflicts
0x2a1a17d1…82c0
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 0xa8667a2e17…3db5e2
Audit this contract →
← previous block·next block →recent activity