← previous blocknext block →recent activity
Analyzing
Block #90,214,044
25 transactions · 24 stateful · 2026-07-25 13:27:56 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,214,044 · 25 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
1w02w13w09w010w111w213w015w317w119w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xae085366…fa10
0x34b655…2a6f
6 touches
3 conflicts
0x481b500f…7ef3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x7e1d87b8…291d
0x34b655…2a6f
4 touches
1 conflict
0x87ab06cc…147e
0x34b655…2a6f
4 touches
1 conflict
0x9816fc81…4f3c
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