← previous blocknext block →recent activity
Analyzing
Block #90,686,876
6 transactions · 6 stateful · 2026-07-27 05:21:41 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,686,876 · 6 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
4 touches
1 conflict
0xaa6f28d9…83ef
0x34b655…2a6f
4 touches
1 conflict
0xb67fdb08…393c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x379dc435…6616
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x1349aa49…4a25
0xbeeffb…5fdb
2 touches
0 conflicts
0xa808ec60…5528
0xbeeffb…5fdb
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 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity