← previous blocknext block →recent activity
Analyzing
Block #100,810,272
17 transactions · 15 stateful · 2026-08-31 17:01:38 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,810,272 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x076b9edf…e35c
0x34b655…2a6f
2 touches
0 conflicts
0x24d47694…e647
0x34b655…2a6f
2 touches
0 conflicts
0x4220bb8a…f472
0x34b655…2a6f
2 touches
0 conflicts
0x43b34fb2…7b88
0x34b655…2a6f
2 touches
0 conflicts
0x5d0464f2…4110
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
1 conflict on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity