← previous blocknext block →recent activity
Analyzing
Block #73,811,056
7 transactions · 6 stateful · 2026-05-11 03:57:14 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,811,056 · 7 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x3e527d42…5f86
0x065c9d…c394
4 touches
1 conflict
0xbdb35945…e93f
0x065c9d…c394
4 touches
1 conflict
0x2484cc15…5afc
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
2 touches
0 conflicts
0xaf498679…7732
0x34b655…2a6f
2 touches
0 conflicts
0x462c8be7…4f83
0x8d66a4…3095
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