← previous blocknext block →recent activity
Analyzing
Block #73,657,692
18 transactions · 17 stateful · 2026-05-10 10:43:03 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,657,692 · 18 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
2w04w05w16w27w08w111w112w213w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38524fae…9deb
0x34b655…2a6f
6 touches
3 conflicts
0x7f81fb82…633e
0x065c9d…c394
6 touches
3 conflicts
0xf2438038…5fa7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x2f6d98a3…5ea6
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
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
3 conflicts on slot 0x38524faed4…ae9deb
Audit this contract →
← previous block·next block →recent activity