← previous blocknext block →recent activity
Analyzing
Block #102,860,843
20 transactions · 17 stateful · 2026-09-07 21:29:17 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,860,843 · 20 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
2w08w09w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0xd1d08056…c46c
0x851145…3f07
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
5 touches
3 conflicts
0x3d9eb674…b3fb
0x754704…b603
4 touches
1 conflict
0x0edf889a…ce9d
0x01bff4…1071
4 touches
1 conflict
0xac241d0f…ff84
0x851145…3f07
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: 0x01bff417…bc1071
15 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity