← previous blocknext block →recent activity
Analyzing
Block #71,044,595
29 transactions · 23 stateful · 2026-04-28 08:29:44 UTC
Parallelism
86/100
Blocked
30%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #71,044,595 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w010w116w117w018w122w123w225w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3981be5…2c47
0x34b655…2a6f
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x46cb45de…a568
0x188d58…ea8e
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x005fb969…2d97
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x0d2947c3…98d6
0x34b655…2a6f
4 touches
1 conflict
0x3254d19b…f714
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
6 conflicts on slot 0xf3981be56e…f02c47
Audit this contract →
← previous block·next block →recent activity