← previous blocknext block →recent activity
Analyzing
Block #73,375,672
6 transactions · 6 stateful · 2026-05-09 03:24:00 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,375,672 · 6 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7fe0d97…ae1c
0x2a68ba…90c5
4 touches
1 conflict
0x1a4b4152…0a08
0x8e764f…e322
4 touches
1 conflict
0x2e2214a9…fe0d
0x8e764f…e322
4 touches
1 conflict
0xe7535190…5a0f
0x8e764f…e322
4 touches
1 conflict
0xe94e77ab…f017
0x8e764f…e322
4 touches
1 conflict
0xf0f673fd…37a7
0x8e764f…e322
4 touches
1 conflict
0x4e766fad…79a6
0xc8689a…ee79
4 touches
1 conflict
0xe038916c…b1be
0x2a68ba…90c5
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: Kuru Exchange: MarginAccount
1 conflict on slot 0xa7fe0d9788…69ae1c
Audit this contract →
← previous block·next block →recent activity