← previous blocknext block →recent activity
Analyzing
Block #102,817,733
20 transactions · 14 stateful · 2026-09-07 17:52:20 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,817,733 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w17w28w015w216w317w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x470b41f6…fc68
0x34b655…2a6f
8 touches
6 conflicts
0xf0dd5e06…93b2
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x06ce5d4b…c122
0x34ae4d…3fc5
4 touches
1 conflict
0x1e602875…e2a7
0x34b655…2a6f
4 touches
1 conflict
0x212a19ca…2dd4
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5fde4971…aac9
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x470b41f691…2dfc68
Audit this contract →
← previous block·next block →recent activity