← previous blocknext block →recent activity
Analyzing
Block #71,044,903
7 transactions · 6 stateful · 2026-04-28 08:31:45 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,044,903 · 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
3w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ab14837…e1b2
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x131a2e…0da9
4 touches
1 conflict
0x5c8c6ab6…dc36
0x131a2e…0da9
3 touches
1 conflict
0x520f0a43…7d22
0x065c9d…c394
2 touches
0 conflicts
0x71ffdb10…1fb5
0x065c9d…c394
2 touches
0 conflicts
0x9c72b24b…a078
0x065c9d…c394
2 touches
0 conflicts
0xf0b9e18d…eac7
0x065c9d…c394
2 touches
0 conflicts
0x4cb2b152…2e00
0x131a2e…0da9
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 0x4ab14837eb…ffe1b2
Audit this contract →
← previous block·next block →recent activity