← previous blocknext block →recent activity
Analyzing
Block #89,678,902
19 transactions · 18 stateful · 2026-07-23 16:27:52 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,678,902 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w110w011w114w015w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xed324c8e…b866
0x34b655…2a6f
6 touches
3 conflicts
0x7a2fc410…c088
0x34b655…2a6f
6 touches
3 conflicts
0xe6852983…205f
0x0a2fbf…29b1
4 touches
1 conflict
0xe6852983…2060
0x0a2fbf…29b1
4 touches
1 conflict
0xe6852983…2063
0x0a2fbf…29b1
4 touches
1 conflict
0x117298b5…75e2
0x34b655…2a6f
4 touches
1 conflict
0x152b716a…ef22
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity