← previous blocknext block →recent activity
Analyzing
Block #90,629,889
12 transactions · 11 stateful · 2026-07-27 00:34:59 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,629,889 · 12 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
5w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x746bcce3…d0ce
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfb72b7b3…0a27
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x3732c6c9…ded6
0x34b655…2a6f
2 touches
0 conflicts
0x6b47245e…a342
0x34b655…2a6f
2 touches
0 conflicts
0x74fd0a9b…3aaa
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 0x746bcce3fa…c7d0ce
Audit this contract →
← previous block·next block →recent activity