← previous blocknext block →recent activity
Analyzing
Block #100,853,785
16 transactions · 16 stateful · 2026-08-31 20:40:44 UTC
Parallelism
63/100
Blocked
31%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,853,785 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x77d0f1e0…d1df
0x40c49f…2af0
9 touches
10 conflicts
0x6518075e…2b17
0x2a68ba…90c5
4 touches
1 conflict
0xa3b5458e…ff0c
0x40c49f…2af0
3 touches
1 conflict
0x513b12c7…47cd
0x34b655…2a6f
2 touches
0 conflicts
0x76622fb2…4f08
0x34b655…2a6f
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
10 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity