← previous blocknext block →recent activity
Analyzing
Block #90,624,373
16 transactions · 14 stateful · 2026-07-27 00:07:14 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,624,373 · 16 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
3w04w16w07w112w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a3b1be…8122
0x34b655…2a6f
8 touches
6 conflicts
0x2751729d…3bb7
0x34b655…2a6f
6 touches
3 conflicts
0x13510de3…1c68
0x34b655…2a6f
4 touches
1 conflict
0x141a3ab6…f2cf
0x34b655…2a6f
4 touches
1 conflict
0x20fbcaee…bb79
0x34b655…2a6f
4 touches
1 conflict
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x350e5d8a…601f
0x34b655…2a6f
4 touches
1 conflict
0x4560e5a8…b741
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xb5a3b1be7c…288122
Audit this contract →
← previous block·next block →recent activity