← previous blocknext block →recent activity
Analyzing
Block #97,545,760
32 transactions · 26 stateful · 2026-08-20 05:45:21 UTC
Parallelism
84/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,545,760 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w09w012w017w119w020w121w223w224w325w426w431w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xcc8faac2…c766
0x065c9d…c394
8 touches
6 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
6 touches
3 conflicts
0x15110fed…83a6
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
4 touches
1 conflict
0x1203ea08…52c3
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity