← previous blocknext block →recent activity
Analyzing
Block #102,043,342
12 transactions · 12 stateful · 2026-09-05 00:31:27 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,043,342 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w09w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6deeb676…a4f2
0x065c9d…c394
5 touches
3 conflicts
0x9ba7d0c8…ec52
0xee8c0e…1242
4 touches
1 conflict
0x00000000…0000
0x354d92…66fb
4 touches
1 conflict
0x00000000…0001
0x354d92…66fb
4 touches
1 conflict
0x38b5b2ce…c5bb
0x354d92…66fb
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xdb9f7f76…18c9
0x754704…b603
4 touches
1 conflict
0x56a919c4…ab49
0xee8c0e…1242
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 0x6deeb676a8…39a4f2
Audit this contract →
← previous block·next block →recent activity