← previous blocknext block →recent activity
Analyzing
Block #108,655,514
18 transactions · 18 stateful · 2026-09-28 04:26:26 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,655,514 · 18 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
3w04w06w17w211w312w416w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x71b64718…0ad1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x7dccee83…c75a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x1fb37a…a010
4 touches
1 conflict
0x1bc6a096…d743
0x34b655…2a6f
4 touches
1 conflict
0x248359b8…98ed
0x34b655…2a6f
4 touches
1 conflict
0xcb45d9d6…cb80
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity