← previous blocknext block →recent activity
Analyzing
Block #72,981,335
16 transactions · 16 stateful · 2026-05-07 07:40:22 UTC
Parallelism
44/100
Blocked
50%
Avg conflicts / tx
2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #72,981,335 · 16 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62d080e9…4a7c
0x34b655…2a6f
14 touches
21 conflicts
0x84143682…30a9
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x908d4442…2c4b
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x55b6a001…1e7a
0x34b655…2a6f
8 touches
6 conflicts
0x7cbd466f…1700
0x34b655…2a6f
8 touches
6 conflicts
0xf853eb8e…4027
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x62d080e928…5a4a7c
Audit this contract →
← previous block·next block →recent activity