← previous blocknext block →recent activity
Analyzing
Block #102,244,388
34 transactions · 24 stateful · 2026-09-05 17:30:35 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,244,388 · 34 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
15w016w117w018w019w121w122w224w025w127w329w431w032w133w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
6 touches
3 conflicts
0x19720b99…9509
0x34b655…2a6f
6 touches
3 conflicts
0x3a106380…1d75
0x34b655…2a6f
4 touches
1 conflict
0x51cfbcbc…fa29
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity