← previous blocknext block →recent activity
Analyzing
Block #72,855,392
8 transactions · 6 stateful · 2026-05-06 17:42:05 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,855,392 · 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe09eda07…8dda
0x2a68ba…90c5
4 touches
1 conflict
0x8d2bd5f8…c59a
0x065c9d…c394
3 touches
1 conflict
0x304ca0d3…f9d6
0x065c9d…c394
3 touches
1 conflict
0xb956234e…e6ef
0x065c9d…c394
3 touches
1 conflict
0x3436b0eb…88cc
0x065c9d…c394
2 touches
1 conflict
0xa69f6e58…ea5a
0x065c9d…c394
2 touches
0 conflicts
0xe49c7589…2b67
0x065c9d…c394
2 touches
0 conflicts
0x70b2f813…783c
0x2a68ba…90c5
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 0xe09eda075e…748dda
Audit this contract →
← previous block·next block →recent activity