← previous blocknext block →recent activity
Analyzing
Block #102,049,183
23 transactions · 18 stateful · 2026-09-05 01:01:02 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,049,183 · 23 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
1w02w16w07w114w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb87af72a…aef6
0x2a68ba…90c5
8 touches
6 conflicts
0x53d8d00d…4af2
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x1f420b26…90da
0x065c9d…c394
2 touches
0 conflicts
0x50951f37…219c
0x3bd359…433a
2 touches
0 conflicts
0x6237f1a7…2f59
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x47bae1…7568
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
6 conflicts on slot 0xb87af72ae5…0baef6
Audit this contract →
← previous block·next block →recent activity