← previous blocknext block →recent activity
Analyzing
Block #73,689,164
8 transactions · 7 stateful · 2026-05-10 14:15:25 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,689,164 · 8 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
1w02w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x529acb6a…fcc6
0x065c9d…c394
4 touches
1 conflict
0x3e733ae4…4598
0x34b655…2a6f
4 touches
1 conflict
0xf2438038…5fa7
0x34b655…2a6f
4 touches
1 conflict
0xde689c6a…7201
0x065c9d…c394
2 touches
0 conflicts
0xae69c125…2379
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x005bcc9d…5141
0x34b655…2a6f
2 touches
0 conflicts
0x19a745e4…205a
0x34b655…2a6f
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: Market-MON/USDC
1 conflict on slot 0x529acb6ad1…f0fcc6
Audit this contract →
← previous block·next block →recent activity