← previous blocknext block →recent activity
Analyzing
Block #102,801,152
32 transactions · 30 stateful · 2026-09-07 16:28:47 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,801,152 · 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
1w02w05w06w17w08w19w217w118w220w221w322w324w025w126w227w330w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9368c6f7…37ba
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xb7b446d2…2006
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd6113c0f…0a4b
0x34b655…2a6f
6 touches
3 conflicts
0x64d501ff…42cf
0x34b655…2a6f
4 touches
1 conflict
0x74e485b1…d380
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: Perpl
6 conflicts on slot 0x9368c6f77d…4b37ba
Audit this contract →
← previous block·next block →recent activity