← previous blocknext block →recent activity
Analyzing
Block #101,657,207
57 transactions · 47 stateful · 2026-09-03 16:03:06 UTC
Parallelism
77/100
Blocked
64%
Avg conflicts / tx
2.05
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #101,657,207 · 57 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w213w214w316w017w118w020w121w222w323w424w525w626w728w829w930w1031w1132w1234w253w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
26 touches
78 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0003
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
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
78 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity