← previous blocknext block →recent activity
Analyzing
Block #90,866,802
7 transactions · 6 stateful · 2026-07-27 20:26:58 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,866,802 · 7 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ae4a85e…c097
0x34b655…2a6f
4 touches
1 conflict
0x663ab2c3…67ab
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe2e52e46…0894
0x34b655…2a6f
4 touches
1 conflict
0x50bd25e8…0b60
0x34b655…2a6f
2 touches
0 conflicts
0x50bd25e8…0b61
0x34b655…2a6f
2 touches
0 conflicts
0x53111a09…966b
0x34b655…2a6f
2 touches
0 conflicts
0x5b4597dd…5003
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 0x6ae4a85e7c…0fc097
Audit this contract →
← previous block·next block →recent activity