← previous blocknext block →recent activity
Analyzing
Block #102,191,488
25 transactions · 23 stateful · 2026-09-05 13:02:33 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,191,488 · 25 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
1w02w03w14w25w06w17w08w09w110w212w120w121w122w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0bb33e3f…7072
0x34b655…2a6f
6 touches
3 conflicts
0x56e0d685…c960
0x34b655…2a6f
4 touches
1 conflict
0x59d2df30…aff2
0x34b655…2a6f
4 touches
1 conflict
0x5f749304…d1c1
0x34b655…2a6f
4 touches
1 conflict
0x60869fed…8266
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity