← previous blocknext block →recent activity
Analyzing
Block #90,553,857
6 transactions · 6 stateful · 2026-07-26 18:12:30 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,553,857 · 6 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9efeab3a…9786
0x34b655…2a6f
4 touches
1 conflict
0xd8d6c5dc…c5f4
0x34b655…2a6f
4 touches
1 conflict
0x4e621c19…6089
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x84f1926d…4f7b
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x3e412550…5c60
0x34b655…2a6f
2 touches
0 conflicts
0x41d39318…d624
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 0x9efeab3a64…fd9786
Audit this contract →
← previous block·next block →recent activity