← previous blocknext block →recent activity
Analyzing
Block #108,515,656
14 transactions · 14 stateful · 2026-09-27 16:42:07 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,515,656 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w19w010w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xfc51df41…9981
0x34b655…2a6f
4 touches
1 conflict
0xb58c5f09…1656
0x34b655…2a6f
4 touches
1 conflict
0xaa3cf307…30e8
0x34b655…2a6f
4 touches
1 conflict
0x65b911b2…d61b
0x34b655…2a6f
4 touches
1 conflict
0x7a06639f…0bdb
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x3af0dd8e…0026
0x1b6862…e19c
2 touches
0 conflicts
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: Kuru Exchange: MarginAccount
1 conflict on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity