← previous blocknext block →recent activity
Analyzing
Block #102,415,745
32 transactions · 27 stateful · 2026-09-06 07:58:47 UTC
Parallelism
91/100
Blocked
30%
Avg conflicts / tx
0.34
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,415,745 · 32 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
1w03w17w110w014w015w116w017w118w222w023w126w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8926b6c…83c7
0x34b655…2a6f
6 touches
3 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
6 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0xd96b70d8…e435
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe3aba92b…0126
0x065c9d…c394
5 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
3 conflicts on slot 0xf8926b6c1e…8583c7
Audit this contract →
← previous block·next block →recent activity