← previous blocknext block →recent activity
Analyzing
Block #90,388,360
21 transactions · 20 stateful · 2026-07-26 04:14:01 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,388,360 · 21 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
1w05w06w17w28w09w110w111w213w317w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x750fb05c…0e99
0x34b655…2a6f
6 touches
3 conflicts
0x08803a9b…dfbd
0x34b655…2a6f
6 touches
3 conflicts
0x9d20b779…6b98
0x34b655…2a6f
4 touches
1 conflict
0x9d349109…9a69
0x34b655…2a6f
4 touches
1 conflict
0xc2ebcc0c…2261
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity