← previous blocknext block →recent activity
Analyzing
Block #90,028,485
14 transactions · 13 stateful · 2026-07-24 21:49:46 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,028,485 · 14 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
1w02w14w05w07w08w110w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9eb27650…bf85
0x34b655…2a6f
4 touches
1 conflict
0xe4955ccc…3311
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x279ddfdc…78fb
0x34b655…2a6f
4 touches
1 conflict
0x279ddfdc…78fc
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
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
1 conflict on slot 0x9eb276500b…d6bf85
Audit this contract →
← previous block·next block →recent activity