← previous blocknext block →recent activity
Analyzing
Block #102,694,700
41 transactions · 32 stateful · 2026-09-07 07:30:09 UTC
Parallelism
73/100
Blocked
66%
Avg conflicts / tx
1.83
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #102,694,700 · 41 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w08w19w210w312w413w514w615w716w118w222w324w425w526w629w730w834w1037w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xfaf5fe80…1ffc
0x34b655…2a6f
8 touches
6 conflicts
0xf0dd0b1d…6cd8
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x08db2444…22b2
0x34b655…2a6f
6 touches
3 conflicts
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: 0xf5b5f7f8…a36d70
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity