← previous blocknext block →recent activity
Analyzing
Block #71,740,969
23 transactions · 14 stateful · 2026-05-01 13:51:09 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #71,740,969 · 23 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
1w02w119w020w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7cbd466f…1700
0x34b655…2a6f
4 touches
1 conflict
0xb96e29a5…0419
0x34b655…2a6f
4 touches
1 conflict
0xe54a1f6f…18f2
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0xff5c097d…680c
0x34b655…2a6f
4 touches
1 conflict
0x55b6a001…1e7a
0x34b655…2a6f
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity