← previous blocknext block →recent activity
Analyzing
Block #102,230,215
27 transactions · 26 stateful · 2026-09-05 16:18:39 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,230,215 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w09w110w211w012w113w215w316w417w023w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8590d68…d5c8
0x34b655…2a6f
8 touches
6 conflicts
0x4cae7e34…1da0
0x34b655…2a6f
8 touches
6 conflicts
0x24b3f7f7…3b29
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xd7908b5f…56b9
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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 0xa8590d682d…9fd5c8
Audit this contract →
← previous block·next block →recent activity