← previous blocknext block →recent activity
Analyzing
Block #90,621,364
18 transactions · 15 stateful · 2026-07-26 23:52:06 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,621,364 · 18 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
6w07w110w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6d8afb6…0f8f
0x34b655…2a6f
4 touches
1 conflict
0x862d2de7…fa71
0x34b655…2a6f
4 touches
1 conflict
0x9eb44196…6ea4
0x34b655…2a6f
4 touches
1 conflict
0xab4aea39…fcaa
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc148f9cc…0924
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0xe6d8afb6b3…6a0f8f
Audit this contract →
← previous block·next block →recent activity