← previous blocknext block →recent activity
Analyzing
Block #90,065,402
14 transactions · 14 stateful · 2026-07-25 00:56:12 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,065,402 · 14 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
1w02w15w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa124184b…1dcb
0x34b655…2a6f
4 touches
1 conflict
0xd2e482cc…0a50
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0xec74c58c…27c2
0x34b655…2a6f
4 touches
1 conflict
0x9feb7f16…58ee
0x34b655…2a6f
4 touches
1 conflict
0x93ecee58…010a
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 0xa124184b0e…fc1dcb
Audit this contract →
← previous block·next block →recent activity