← previous blocknext block →recent activity
Analyzing
Block #73,374,501
16 transactions · 13 stateful · 2026-05-09 03:16:13 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,374,501 · 16 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
1w04w05w16w27w38w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1441ea6c…b153
0x065c9d…c394
2 touches
0 conflicts
0x1fe6761b…6dc7
0x065c9d…c394
2 touches
0 conflicts
0x34339bb8…f5f5
0x065c9d…c394
2 touches
0 conflicts
0x64a2bbe5…8815
0x065c9d…c394
2 touches
0 conflicts
0x73a654be…23ac
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: 0xab35264b…1cfa38
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity