← previous blocknext block →recent activity
Analyzing
Block #73,202,424
11 transactions · 11 stateful · 2026-05-08 08:11:29 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,202,424 · 11 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
2w05w16w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x7f189cf6…afab
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x96a45cb8…7e8d
0x065c9d…c394
4 touches
1 conflict
0xc3c0f47e…7666
0x065c9d…c394
4 touches
1 conflict
0x75665387…2a55
0x065c9d…c394
3 touches
1 conflict
0x20174123…b5ff
0x065c9d…c394
3 touches
1 conflict
0xc275b4c3…07d7
0x065c9d…c394
3 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
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity