← previous blocknext block →recent activity
Analyzing
Block #108,495,548
23 transactions · 19 stateful · 2026-09-27 15:00:53 UTC
Parallelism
87/100
Blocked
32%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,495,548 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w08w19w010w115w217w018w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a663e9a…a9c7
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9cb
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9ca
0x508254…98bd
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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: 0x508254c8…4a98bd
1 conflict on slot 0x3a663e9a3a…2fa9c7
Audit this contract →
← previous block·next block →recent activity