← previous blocknext block →recent activity
Analyzing
Block #90,643,533
4 transactions · 3 stateful · 2026-07-27 01:43:38 UTC
Parallelism
50/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,643,533 · 4 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c09c53e…64b4
0x34b655…2a6f
4 touches
1 conflict
0x159cff26…7665
0x34b655…2a6f
4 touches
1 conflict
0xe060ebb9…005a
0x34b655…2a6f
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
2 touches
0 conflicts
0x1cdd5d15…9e8d
0x34b655…2a6f
2 touches
0 conflicts
0x1da820ae…c04a
0x34b655…2a6f
2 touches
0 conflicts
0x44df3c2a…bafe
0x34b655…2a6f
2 touches
0 conflicts
0x44df3c2a…baff
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 0x7c09c53e5b…3864b4
Audit this contract →
← previous block·next block →recent activity