← previous blocknext block →recent activity
Analyzing
Block #90,810,457
18 transactions · 18 stateful · 2026-07-27 15:43:26 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,810,457 · 18 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
2w04w05w110w112w013w115w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e4f2109…e676
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
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 0x1e4f21091b…bbe676
Audit this contract →
← previous block·next block →recent activity