← previous blocknext block →recent activity
Analyzing
Block #102,468,247
23 transactions · 21 stateful · 2026-09-06 12:24:44 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,468,247 · 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
2w04w05w16w17w08w212w013w117w018w119w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca3bb3ee…99d7
0x065c9d…c394
5 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0x02372d42…1871
0x34b655…2a6f
4 touches
1 conflict
0x0eec68d6…e112
0x34b655…2a6f
4 touches
1 conflict
0x53e08444…d671
0x34b655…2a6f
4 touches
1 conflict
0x6c7c1a4b…5751
0x34b655…2a6f
4 touches
1 conflict
0x6dc1811e…2588
0x34b655…2a6f
4 touches
1 conflict
0x73ae20cb…19f1
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: Market-MON/USDC
3 conflicts on slot 0xca3bb3eef7…7f99d7
Audit this contract →
← previous block·next block →recent activity