← previous blocknext block →recent activity
Analyzing
Block #102,096,300
29 transactions · 20 stateful · 2026-09-05 05:00:02 UTC
Parallelism
79/100
Blocked
30%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,096,300 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w016w017w120w121w222w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d6d36e9…9fb4
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd1298d17…d8a1
0x34b655…2a6f
8 touches
6 conflicts
0x1f4e6c86…7789
0x34b655…2a6f
6 touches
3 conflicts
0x64275949…d698
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3f5831e5…02b2
0x34b655…2a6f
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
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 0x6d6d36e95c…459fb4
Audit this contract →
← previous block·next block →recent activity