← previous blocknext block →recent activity
Analyzing
Block #89,577,939
16 transactions · 15 stateful · 2026-07-23 05:48:49 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
0.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,577,939 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w18w311w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x861e5aef…d32c
0x34b655…2a6f
6 touches
3 conflicts
0x266a6b2c…4376
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4377
0x34b655…2a6f
4 touches
1 conflict
0x38902419…bb3b
0x34b655…2a6f
4 touches
1 conflict
0x4d733e52…73bf
0x34b655…2a6f
4 touches
1 conflict
0x51deae08…37a2
0x34b655…2a6f
4 touches
1 conflict
0x6a2ebbdd…0438
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity