← previous blocknext block →recent activity
Analyzing
Block #100,736,032
24 transactions · 23 stateful · 2026-08-31 10:47:58 UTC
Parallelism
71/100
Blocked
39%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,736,032 · 24 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
1w05w06w17w09w110w211w312w413w515w018w122w623w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0xe653f472…8cf4
0x851145…3f07
11 touches
15 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa242e227…2e45
0x34b655…2a6f
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
15 conflicts on slot 0x07b86c515d…73cdae
Audit this contract →
← previous block·next block →recent activity