← previous blocknext block →recent activity
Analyzing
Block #89,566,043
19 transactions · 15 stateful · 2026-07-23 04:29:20 UTC
Parallelism
89/100
Blocked
20%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,566,043 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w110w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
2 touches
0 conflicts
0xa7faa737…ff2b
0x065c9d…c394
2 touches
0 conflicts
0xce827910…ff22
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
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 0x301e1c776c…3b9e30
Audit this contract →
← previous block·next block →recent activity