← previous blocknext block →recent activity
Analyzing
Block #71,043,213
26 transactions · 17 stateful · 2026-04-28 08:20:30 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,043,213 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w010w113w017w118w220w021w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0x1c389468…6b0e
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xf476568d…6105
0x065c9d…c394
3 touches
1 conflict
0x99988a15…8d81
0x065c9d…c394
3 touches
1 conflict
0x8e572361…3880
0x122c0d…e3fa
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
3 conflicts on slot 0xc3c8642ae9…317da5
Audit this contract →
← previous block·next block →recent activity