← previous blocknext block →recent activity
Analyzing
Block #102,327,179
24 transactions · 22 stateful · 2026-09-06 00:30:04 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,327,179 · 24 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
2w04w07w08w110w211w313w017w118w219w320w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xed7428d1…013c
0x34b655…2a6f
6 touches
3 conflicts
0x898d9b8a…d1ef
0x34b655…2a6f
6 touches
3 conflicts
0xb1927b58…f161
0x34b655…2a6f
4 touches
2 conflicts
0x359866c7…de7b
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6572
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4ac4a2c2…2707
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity