← previous blocknext block →recent activity
Analyzing
Block #89,679,400
15 transactions · 14 stateful · 2026-07-23 16:30:23 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,679,400 · 15 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
5w06w17w08w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71a3fd70…4a5b
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x3cebc8f1…975c
0xe52b14…7230
2 touches
0 conflicts
0x51232c8c…f30c
0xe52b14…7230
2 touches
0 conflicts
0x51232c8c…f30e
0xe52b14…7230
2 touches
0 conflicts
0x58733c38…f2cd
0xe52b14…7230
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 0x71a3fd7023…ce4a5b
Audit this contract →
← previous block·next block →recent activity