← previous blocknext block →recent activity
Analyzing
Block #76,196,195
10 transactions · 9 stateful · 2026-05-22 05:16:59 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,196,195 · 10 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0xd551efa3…11be
0x065c9d…c394
4 touches
1 conflict
0x88525d31…4125
0x065c9d…c394
3 touches
1 conflict
0x593965cd…09c9
0x065c9d…c394
3 touches
1 conflict
0x062ff89f…4fff
0x065c9d…c394
2 touches
0 conflicts
0x070042f4…eea4
0x065c9d…c394
2 touches
0 conflicts
0xc2820b1c…b3bb
0x065c9d…c394
2 touches
0 conflicts
0xdb13b55e…ef6b
0x065c9d…c394
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: Market-MON/USDC
1 conflict on slot 0xfe2bac2b2f…482cec
Audit this contract →
← previous block·next block →recent activity