← previous blocknext block →recent activity
Analyzing
Block #89,403,905
18 transactions · 16 stateful · 2026-07-22 10:26:08 UTC
Parallelism
89/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,403,905 · 18 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
1w02w14w05w18w09w110w112w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa98c6e8…0748
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x34d4ef1a…0345
0x34b655…2a6f
4 touches
1 conflict
0x37ee30c9…9e70
0x34b655…2a6f
4 touches
1 conflict
0x4ed4b5be…d1a6
0x34b655…2a6f
4 touches
1 conflict
0x508bbf1b…fe95
0x34b655…2a6f
4 touches
1 conflict
0x5fde4971…aac9
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 0xfa98c6e8d1…a10748
Audit this contract →
← previous block·next block →recent activity