← previous blocknext block →recent activity
Analyzing
Block #99,625,620
28 transactions · 23 stateful · 2026-08-27 13:29:01 UTC
Parallelism
89/100
Blocked
35%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,625,620 · 28 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
1w03w04w16w29w010w013w119w221w022w223w124w126w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x14def591…385e
0x851145…3f07
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xf7640726…19a2
0x2a68ba…90c5
4 touches
1 conflict
0x08d53462…97ef
0x2b46c0…1669
4 touches
1 conflict
0x5a409e7f…09b6
0x2b46c0…1669
4 touches
1 conflict
0x7a12283f…b18a
0x2b46c0…1669
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: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity