← previous blocknext block →recent activity
Analyzing
Block #72,310,396
19 transactions · 17 stateful · 2026-05-04 05:10:14 UTC
Parallelism
74/100
Blocked
59%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,310,396 · 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
1w02w13w04w16w18w09w110w211w213w315w417w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b7bcac3…8fbf
0x34b655…2a6f
10 touches
10 conflicts
0xf823e97f…2ee6
0x065c9d…c394
8 touches
6 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
6 touches
3 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
6 touches
3 conflicts
0x2877f440…c2c8
0x34b655…2a6f
6 touches
3 conflicts
0x3254d19b…f714
0x34b655…2a6f
6 touches
3 conflicts
0x414e9446…4b59
0x34b655…2a6f
6 touches
3 conflicts
0x568f8542…b150
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x7b7bcac3fe…968fbf
Audit this contract →
← previous block·next block →recent activity