← previous blocknext block →recent activity
Analyzing
Block #73,595,293
13 transactions · 10 stateful · 2026-05-10 03:44:40 UTC
Parallelism
77/100
Blocked
30%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,595,293 · 13 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
1w06w07w18w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x2f6503c3…b11b
0x065c9d…c394
4 touches
1 conflict
0x1b46bcf1…13b3
0x065c9d…c394
4 touches
1 conflict
0x2806aa15…cab8
0x065c9d…c394
3 touches
1 conflict
0xe95efb36…ab71
0x065c9d…c394
3 touches
1 conflict
0x0aa7d9ad…f2cc
0x065c9d…c394
3 touches
1 conflict
0x0892bc14…5ba2
0x065c9d…c394
3 touches
1 conflict
0xe2a0a4eb…676c
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity