← previous blocknext block →recent activity
Analyzing
Block #90,622,946
13 transactions · 13 stateful · 2026-07-27 00:00:04 UTC
Parallelism
62/100
Blocked
46%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,622,946 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w29w310w412w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0x3cebc8f1…975c
0xe52b14…7230
4 touches
1 conflict
0xd4e69a1d…6139
0xe52b14…7230
4 touches
1 conflict
0xee8defd7…73c4
0xe52b14…7230
4 touches
1 conflict
0xef7c06bc…c2eb
0xe52b14…7230
4 touches
1 conflict
0x7032dc14…49ea
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xaa9f27b0…9cf2
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: 0xe52b1424…bb7230
10 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity