← previous blocknext block →recent activity
Analyzing
Block #90,833,937
17 transactions · 15 stateful · 2026-07-27 17:41:36 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,833,937 · 17 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
3w05w17w111w213w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26d1c221…4d2a
0x34b655…2a6f
4 touches
1 conflict
0x058456b1…5eb1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x1aa62c36…420a
0x34b655…2a6f
2 touches
0 conflicts
0x2991946f…45cd
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 0x26d1c221d7…ef4d2a
Audit this contract →
← previous block·next block →recent activity