← previous blocknext block →recent activity
Analyzing
Block #90,313,315
11 transactions · 11 stateful · 2026-07-25 21:49:59 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,313,315 · 11 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
1w04w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb64a26cd…4ffa
0x34b655…2a6f
4 touches
1 conflict
0x17aad0b2…59d0
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0e7a1107…bf62
0x34b655…2a6f
2 touches
0 conflicts
0x12bdece2…85bc
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
2 touches
0 conflicts
0x9a36cb2e…0929
0x34b655…2a6f
2 touches
0 conflicts
0xc755c95b…6814
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 0xb64a26cd1b…374ffa
Audit this contract →
← previous block·next block →recent activity