← previous blocknext block →recent activity
Analyzing
Block #76,246,826
12 transactions · 10 stateful · 2026-05-22 10:54:25 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,246,826 · 12 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
1w06w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5bfc8fb…071f
0x2a68ba…90c5
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x68dec6e2…5eb2
0xa6afd3…d132
3 touches
1 conflict
0xf413d759…6da4
0x065c9d…c394
2 touches
0 conflicts
0x0aa885fa…a3d1
0x2a68ba…90c5
2 touches
0 conflicts
0xa980598e…ec52
0x3bd359…433a
2 touches
0 conflicts
0xa1087a5c…66c4
0x754704…b603
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 0xd5bfc8fb99…70071f
Audit this contract →
← previous block·next block →recent activity