← previous blocknext block →recent activity
Analyzing
Block #108,508,752
19 transactions · 19 stateful · 2026-09-27 16:07:21 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,508,752 · 19 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
4w05w17w08w19w010w011w112w213w314w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x67d1be…196f
4 touches
1 conflict
0x2b936aa5…05e5
0x141b1d…9583
4 touches
1 conflict
0x09196c78…4d65
0x34b655…2a6f
4 touches
1 conflict
0x19dcf812…44d9
0x34b655…2a6f
4 touches
1 conflict
0x1d6cb721…c88c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x555b9368…2989
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: 0x67d1be51…42196f
1 conflict on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity