← previous blocknext block →recent activity
Analyzing
Block #100,140,920
21 transactions · 16 stateful · 2026-08-29 08:49:58 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,140,920 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w211w016w117w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x50c61506…343f
0x34b655…2a6f
4 touches
1 conflict
0x5ddba9ad…6622
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xfb35bb9e…b4be
0x065c9d…c394
3 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
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