← previous blocknext block →recent activity
Analyzing
Block #72,395,291
12 transactions · 10 stateful · 2026-05-04 14:35:49 UTC
Parallelism
75/100
Blocked
30%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,395,291 · 12 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
1w02w18w210w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfca3cd0…5023
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x185ab331…7c16
0xd32edf…ff58
3 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x105ed58f…f3a4
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x5ff611d5…b6cd
0x065c9d…c394
2 touches
0 conflicts
0xfd6b9506…0329
0x065c9d…c394
2 touches
0 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
1 conflict on slot 0xbfca3cd067…cd5023
Audit this contract →
← previous block·next block →recent activity