← previous blocknext block →recent activity
Analyzing
Block #102,738,139
21 transactions · 19 stateful · 2026-09-07 11:08:42 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,738,139 · 21 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
1w03w16w08w09w111w212w313w315w416w118w019w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd5e68f…2a12
0x34b655…2a6f
6 touches
3 conflicts
0xb856d1a1…1f18
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x38e18432…0ad3
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xa9371684…df38
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 0xfcd5e68f28…382a12
Audit this contract →
← previous block·next block →recent activity