← previous blocknext block →recent activity
Analyzing
Block #90,961,454
17 transactions · 15 stateful · 2026-07-28 04:23:05 UTC
Parallelism
76/100
Blocked
27%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,961,454 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w09w110w211w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x966d72e7…a32e
0x34b655…2a6f
6 touches
3 conflicts
0xb2fa1675…4e07
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x69aed638…fbf5
0x34b655…2a6f
4 touches
1 conflict
0x6c0e32fc…a6ca
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9cf9008a…d826
0x34b655…2a6f
4 touches
1 conflict
0xa6a26c30…d8c8
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
3 conflicts on slot 0x966d72e72f…62a32e
Audit this contract →
← previous block·next block →recent activity