← previous blocknext block →recent activity
Analyzing
Block #72,266,643
26 transactions · 18 stateful · 2026-05-04 00:17:03 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,266,643 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w014w015w117w018w120w122w223w124w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6c9bf9b…ac02
0x34b655…2a6f
6 touches
3 conflicts
0x01a33778…c2d4
0x34b655…2a6f
6 touches
3 conflicts
0xac808a27…82db
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4b268018…02fb
0x34b655…2a6f
4 touches
1 conflict
0x964a05c8…3452
0x065c9d…c394
4 touches
1 conflict
0x119cc9e1…c4a4
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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
3 conflicts on slot 0xf6c9bf9b65…e4ac02
Audit this contract →
← previous block·next block →recent activity