← previous blocknext block →recent activity
Analyzing
Block #102,489,613
29 transactions · 24 stateful · 2026-09-06 14:13:04 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,489,613 · 29 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
1w02w03w14w27w110w112w019w121w122w023w126w027w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x359866c7…de7b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xb31eb7d3…64eb
0xa6afd3…d132
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd53bdef3…7d4b
0x34b655…2a6f
4 touches
1 conflict
0xdee4c27f…f1cd
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 0x359866c739…efde7b
Audit this contract →
← previous block·next block →recent activity