← previous blocknext block →recent activity
Analyzing
Block #90,835,721
10 transactions · 10 stateful · 2026-07-27 17:50:35 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,835,721 · 10 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
2w03w14w05w27w39w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0dd34dc…0233
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x86c98782…f3b7
0x34b655…2a6f
4 touches
1 conflict
0xa8dad04b…f666
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc7277122…8339
0x34b655…2a6f
3 touches
1 conflict
0x1aa62c36…420a
0x34b655…2a6f
2 touches
0 conflicts
0x30871fa4…1eba
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 0xb0dd34dc2c…650233
Audit this contract →
← previous block·next block →recent activity