← previous blocknext block →recent activity
Analyzing
Block #100,790,688
23 transactions · 21 stateful · 2026-08-31 15:23:05 UTC
Parallelism
78/100
Blocked
48%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,790,688 · 23 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
1w02w13w04w16w27w310w011w112w213w114w015w116w421w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
8 touches
6 conflicts
0x55192654…91fe
0x34b655…2a6f
8 touches
6 conflicts
0xc7a898a7…501b
0x851145…3f07
7 touches
6 conflicts
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0xdc9915b5…542c
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0xea2d3331…6e33
0x1b6862…e19c
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
6 conflicts on slot 0x07b86c515d…73cdae
Audit this contract →
← previous block·next block →recent activity