← previous blocknext block →recent activity
Analyzing
Block #72,296,872
22 transactions · 18 stateful · 2026-05-04 03:40:07 UTC
Parallelism
77/100
Blocked
56%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,296,872 · 22 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
3w04w16w08w09w110w211w114w215w316w217w420w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb1747e2…f78b
0x34b655…2a6f
10 touches
10 conflicts
0xbbee74c2…567a
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
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
0x579befae…9985
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 0xbb1747e217…82f78b
Audit this contract →
← previous block·next block →recent activity