← previous blocknext block →recent activity
Analyzing
Block #102,800,080
19 transactions · 17 stateful · 2026-09-07 16:23:23 UTC
Parallelism
68/100
Blocked
29%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,800,080 · 19 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
2w09w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2934b4e7…bd5e
0x40c49f…2af0
12 touches
15 conflicts
0x6518075e…2b17
0x2a68ba…90c5
12 touches
15 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x06ce5d4b…c122
0x34ae4d…3fc5
2 touches
0 conflicts
0x12a9b76e…cb76
0x3bd359…433a
2 touches
0 conflicts
0x44ed742f…63f5
0x3bd359…433a
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
15 conflicts on slot 0x2934b4e7e7…27bd5e
Audit this contract →
← previous block·next block →recent activity