← previous blocknext block →recent activity
Analyzing
Block #102,816,688
18 transactions · 18 stateful · 2026-09-07 17:47:05 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,816,688 · 18 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
2w03w110w011w112w213w314w416w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1f93920…915e
0x40c49f…2af0
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x6518075e…2b17
0x2a68ba…90c5
9 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002b
0x1b6862…e19c
2 touches
0 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: 0x40c49f17…d22af0
10 conflicts on slot 0xc1f93920e2…c4915e
Audit this contract →
← previous block·next block →recent activity