← previous blocknext block →recent activity
Analyzing
Block #102,280,536
16 transactions · 14 stateful · 2026-09-05 20:33:50 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,280,536 · 16 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
2w05w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x193f19c1…f4fc
0x065c9d…c394
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x1fd37ed2…3233
0x065c9d…c394
3 touches
1 conflict
0x8c061f1e…3c3f
0x065c9d…c394
3 touches
1 conflict
0x12398fcf…b8e5
0x34b655…2a6f
2 touches
0 conflicts
0x255b4bb2…4a70
0x34b655…2a6f
2 touches
0 conflicts
0x29316387…6612
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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 0x193f19c185…faf4fc
Audit this contract →
← previous block·next block →recent activity