← previous blocknext block →recent activity
Analyzing
Block #89,567,276
17 transactions · 16 stateful · 2026-07-23 04:37:35 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.35
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,567,276 · 17 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
1w02w16w07w18w110w114w015w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15ae3bf3…2507
0x34b655…2a6f
4 touches
1 conflict
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x98fc5672…13c7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x15ae3bf3e8…502507
Audit this contract →
← previous block·next block →recent activity