← previous blocknext block →recent activity
Analyzing
Block #90,293,713
15 transactions · 12 stateful · 2026-07-25 20:10:19 UTC
Parallelism
87/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,293,713 · 15 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
4w05w18w09w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2697123c…8526
0x34b655…2a6f
4 touches
1 conflict
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x97b966d8…6d29
0x34b655…2a6f
4 touches
1 conflict
0xc9299e54…b927
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
2 touches
0 conflicts
0xdb067026…9eb8
0x2b46c0…1669
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 0x2697123ce4…5e8526
Audit this contract →
← previous block·next block →recent activity