← previous blocknext block →recent activity
Analyzing
Block #90,206,012
20 transactions · 17 stateful · 2026-07-25 12:47:28 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,206,012 · 20 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
1w02w13w04w16w09w110w012w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0181bb37…6628
0x34b655…2a6f
4 touches
1 conflict
0x0181bb37…6629
0x34b655…2a6f
4 touches
1 conflict
0x312e4698…54c0
0x34b655…2a6f
4 touches
1 conflict
0x4d1c2806…5947
0x34b655…2a6f
4 touches
1 conflict
0x78346476…4311
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7b211ab8…e32c
0x34b655…2a6f
4 touches
1 conflict
0x98b22a44…2d63
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
1 conflict on slot 0x0181bb3798…ed6628
Audit this contract →
← previous block·next block →recent activity