← previous blocknext block →recent activity
Analyzing
Block #102,527,018
23 transactions · 22 stateful · 2026-09-06 17:22:51 UTC
Parallelism
78/100
Blocked
32%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,527,018 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w010w213w115w016w119w020w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x834128b8…1616
0x34b655…2a6f
6 touches
3 conflicts
0x692e7382…d831
0x34b655…2a6f
4 touches
1 conflict
0x842b957b…2757
0x34b655…2a6f
4 touches
1 conflict
0x8909d9c5…2c56
0x34b655…2a6f
4 touches
1 conflict
0x9ee824ec…5faa
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity