← previous blocknext block →recent activity
Analyzing
Block #89,868,982
16 transactions · 16 stateful · 2026-07-24 08:26:51 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,868,982 · 16 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
1w02w05w17w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x70cfbacf…5c46
0x34b655…2a6f
4 touches
1 conflict
0x0bdb8a7e…608f
0x0a2fbf…29b1
4 touches
1 conflict
0xac10f035…99e6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x0bdb8a7e…608b
0x0a2fbf…29b1
4 touches
1 conflict
0x379dc435…6616
0x34b655…2a6f
4 touches
1 conflict
0x55b4e430…44cb
0x754704…b603
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity