← previous blocknext block →recent activity
Analyzing
Block #108,641,048
29 transactions · 23 stateful · 2026-09-28 03:13:37 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,641,048 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w17w29w313w014w115w216w318w419w526w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x5f72d58f…c445
0x34b655…2a6f
6 touches
3 conflicts
0xfcdb5918…2b49
0x34b655…2a6f
6 touches
3 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
6 touches
3 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
4 touches
1 conflict
0x2b2f1d91…323f
0x34b655…2a6f
4 touches
1 conflict
0x38a1ffff…3a8b
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
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity