← previous blocknext block →recent activity
Analyzing
Block #108,948,643
16 transactions · 13 stateful · 2026-09-29 05:05:41 UTC
Parallelism
75/100
Blocked
46%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,948,643 · 16 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
1w02w16w27w39w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c539d94…b63a
0x34b655…2a6f
6 touches
3 conflicts
0x654b9aa2…7511
0x34b655…2a6f
6 touches
3 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0056
0x1b6862…e19c
4 touches
1 conflict
0xcbf03260…89b0
0x1b6862…e19c
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 0x2c539d94d7…4ab63a
Audit this contract →
← previous block·next block →recent activity