← previous blocknext block →recent activity
Analyzing
Block #89,696,658
14 transactions · 13 stateful · 2026-07-23 17:57:27 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,696,658 · 14 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
7w08w110w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348ae643…36cb
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x05c658d7…ad44
0x065c9d…c394
2 touches
0 conflicts
0x08bc8883…dd3d
0x065c9d…c394
2 touches
0 conflicts
0x19b2189b…c1c5
0x065c9d…c394
2 touches
0 conflicts
0x6b3b6910…9bdd
0x065c9d…c394
2 touches
0 conflicts
0x915bc31c…75a1
0x065c9d…c394
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 0x348ae6432b…d236cb
Audit this contract →
← previous block·next block →recent activity