← previous blocknext block →recent activity
Analyzing
Block #104,024,111
12 transactions · 11 stateful · 2026-09-11 23:17:05 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,024,111 · 12 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
2w03w04w05w16w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39126904…24d8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x939cdd56…00c8
0x34b655…2a6f
4 touches
1 conflict
0xb575cf74…fbd5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x9efe106e…72d2
0x34b655…2a6f
4 touches
1 conflict
0x36f837bd…847f
0x34b655…2a6f
2 touches
0 conflicts
0x3a5cd535…3546
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 0x3912690479…5424d8
Audit this contract →
← previous block·next block →recent activity