← previous blocknext block →recent activity
Analyzing
Block #72,978,215
15 transactions · 15 stateful · 2026-05-07 07:19:33 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,978,215 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w210w011w312w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x388e001a…7e04
0x34b655…2a6f
6 touches
3 conflicts
0xac8e97a0…8426
0x34b655…2a6f
6 touches
3 conflicts
0x9776ae1b…1a92
0x34b655…2a6f
6 touches
3 conflicts
0x6c44331f…9735
0x34b655…2a6f
4 touches
1 conflict
0x7170c140…36bc
0x34b655…2a6f
4 touches
1 conflict
0x7cbd466f…1700
0x34b655…2a6f
4 touches
1 conflict
0xc6417de0…2191
0xc8689a…ee79
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