← previous blocknext block →recent activity
Analyzing
Block #90,705,784
16 transactions · 14 stateful · 2026-07-27 06:56:47 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,705,784 · 16 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
10w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad862891…5d02
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x7b42f6a7…f49c
0x34b655…2a6f
4 touches
1 conflict
0xc1232d65…5194
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5a7eb2ab…75a0
0x34b655…2a6f
2 touches
0 conflicts
0x6767539b…f211
0x34b655…2a6f
2 touches
0 conflicts
0x6f988a4a…b39f
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 0xad862891a0…315d02
Audit this contract →
← previous block·next block →recent activity