← previous blocknext block →recent activity
Analyzing
Block #99,210,850
19 transactions · 14 stateful · 2026-08-26 02:34:09 UTC
Parallelism
89/100
Blocked
21%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,210,850 · 19 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
1w09w110w015w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x21940a20…d7ff
0xd32edf…ff58
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x12c575f4…a0a6
0x065c9d…c394
2 touches
0 conflicts
0x441cbd2e…1814
0x065c9d…c394
2 touches
0 conflicts
0x7bab646a…5e72
0x065c9d…c394
2 touches
0 conflicts
0xec665f88…05ad
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: MarginAccount
1 conflict on slot 0x1125877469…519892
Audit this contract →
← previous block·next block →recent activity