← previous blocknext block →recent activity
Analyzing
Block #108,576,430
15 transactions · 13 stateful · 2026-09-27 21:48:13 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,576,430 · 15 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
1w02w13w26w07w18w210w011w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0x5ff2657f…c133
0xa6afd3…d132
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x4292a836…9ed5
0x34b655…2a6f
4 touches
1 conflict
0x88065e57…c867
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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: 0x80c74517…647210
3 conflicts on slot 0x0000000000…00004c
Audit this contract →
← previous block·next block →recent activity