← previous blocknext block →recent activity
Analyzing
Block #102,216,582
23 transactions · 18 stateful · 2026-09-05 15:09:43 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,216,582 · 23 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
1w014w015w116w017w118w220w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0005a008…264a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0x3c70ac8d…eaf2
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0xac0165b3…889e
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
3 conflicts on slot 0x0005a008c4…88264a
Audit this contract →
← previous block·next block →recent activity