← previous blocknext block →recent activity
Analyzing
Block #75,598,697
9 transactions · 8 stateful · 2026-05-19 10:54:25 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,598,697 · 9 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
1w02w03w16w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x17cd1479…00bb
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a9
0x8d66a4…3095
4 touches
1 conflict
0xb20bd482…8b48
0x065c9d…c394
3 touches
1 conflict
0xba5743c7…21c1
0x1b6862…e19c
2 touches
0 conflicts
0x4bef88e0…eaca
0x3bd359…433a
2 touches
0 conflicts
0xc5c4c1d1…2145
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0003
0x5e60bc…fe22
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
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity