← previous blocknext block →recent activity
Analyzing
Block #73,671,672
20 transactions · 18 stateful · 2026-05-10 12:17:17 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,671,672 · 20 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
1w02w03w14w05w06w17w08w19w210w313w116w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xf2438038…5fa7
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ab
0x8d66a4…3095
6 touches
3 conflicts
0x529acb6a…fcc6
0x065c9d…c394
4 touches
1 conflict
0x64298fc4…bfc7
0x065c9d…c394
4 touches
1 conflict
0xc042d97a…e609
0x065c9d…c394
4 touches
1 conflict
0xdca46ff7…b9d5
0x065c9d…c394
4 touches
1 conflict
0xee8fbd15…423c
0x065c9d…c394
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity