← previous blocknext block →recent activity
Analyzing
Block #100,792,442
20 transactions · 18 stateful · 2026-08-31 15:31:55 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,792,442 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w17w18w29w310w411w512w114w115w016w218w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0x87ed8a8c…07f2
0x851145…3f07
9 touches
10 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x5364bbf4…5b6b
0x851145…3f07
5 touches
3 conflicts
0x18a01188…42f0
0x851145…3f07
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
10 conflicts on slot 0x07b86c515d…73cdae
Audit this contract →
← previous block·next block →recent activity