← previous blocknext block →recent activity
Analyzing
Block #89,540,473
22 transactions · 20 stateful · 2026-07-23 01:38:29 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,540,473 · 22 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
1w09w010w111w013w215w116w220w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x536f894b…2597
0x34b655…2a6f
6 touches
3 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x2debe664…1818
0x34b655…2a6f
4 touches
1 conflict
0x2efac4f6…3abf
0x34b655…2a6f
4 touches
1 conflict
0x3e505a15…70f8
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
3 conflicts on slot 0x536f894bd4…e82597
Audit this contract →
← previous block·next block →recent activity