← previous blocknext block →recent activity
Analyzing
Block #102,486,365
15 transactions · 14 stateful · 2026-09-06 13:56:33 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,486,365 · 15 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
4w09w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x7b43175c…1309
0x928dc8…8207
4 touches
1 conflict
0x18867da9…f322
0x065c9d…c394
3 touches
1 conflict
0x0ffac39e…6d34
0x34b655…2a6f
2 touches
0 conflicts
0x160fee65…8195
0x34b655…2a6f
2 touches
0 conflicts
0x21adef83…f2b7
0x34b655…2a6f
2 touches
0 conflicts
0x41aa4da3…3a1a
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: Market-MON/USDC
1 conflict on slot 0x892daf6e5d…6d48d8
Audit this contract →
← previous block·next block →recent activity