← previous blocknext block →recent activity
Analyzing
Block #102,344,720
32 transactions · 26 stateful · 2026-09-06 01:58:59 UTC
Parallelism
88/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,344,720 · 32 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
3w04w16w27w010w011w115w216w118w324w125w330w031w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb87af72a…aef6
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x451066eb…2e20
0x065c9d…c394
5 touches
3 conflicts
0x00f7e3b7…e017
0x188d58…ea8e
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x56a284d9…32e4
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
6 conflicts on slot 0xb87af72ae5…0baef6
Audit this contract →
← previous block·next block →recent activity