← previous blocknext block →recent activity
Analyzing
Block #90,240,201
23 transactions · 22 stateful · 2026-07-25 15:39:48 UTC
Parallelism
78/100
Blocked
45%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,240,201 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w08w011w212w113w215w316w317w118w320w021w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb69dd898…3e02
0x34b655…2a6f
8 touches
6 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
8 touches
6 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x20492d53…80f9
0x34b655…2a6f
4 touches
1 conflict
0x2bad40ae…0522
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xb69dd89873…193e02
Audit this contract →
← previous block·next block →recent activity