← previous blocknext block →recent activity
Analyzing
Block #102,050,326
14 transactions · 13 stateful · 2026-09-05 01:06:51 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,050,326 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w08w111w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdb8288e3…7979
0x34b655…2a6f
4 touches
1 conflict
0x02372d42…1871
0x34b655…2a6f
2 touches
0 conflicts
0x04f75adb…7b3c
0x34b655…2a6f
2 touches
0 conflicts
0x173b64af…6c43
0x34b655…2a6f
2 touches
0 conflicts
0x2e957c13…4777
0x34b655…2a6f
2 touches
0 conflicts
0x3fb3f2e2…fef3
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity