← previous blocknext block →recent activity
Analyzing
Block #100,862,283
19 transactions · 16 stateful · 2026-08-31 21:23:28 UTC
Parallelism
68/100
Blocked
31%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,862,283 · 19 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
9w010w111w212w313w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6518075e…2b17
0x2a68ba…90c5
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xbe0bb6d1…25cb
0x40c49f…2af0
9 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xe68f7ea1…291f
0x40c49f…2af0
3 touches
1 conflict
0x0e18d182…0425
0x34b655…2a6f
2 touches
0 conflicts
0x3c7c65d0…0b52
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 0x6518075e89…5f2b17
Audit this contract →
← previous block·next block →recent activity