← previous blocknext block →recent activity
Analyzing
Block #108,396,398
14 transactions · 13 stateful · 2026-09-27 06:41:48 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,396,398 · 14 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
1w03w05w17w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x758672cf…c368
0x34b655…2a6f
6 touches
3 conflicts
0x30d077fe…181f
0x34b655…2a6f
4 touches
1 conflict
0x62e9b91f…41fa
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x970da48a…345b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb58c5f09…1656
0x34b655…2a6f
4 touches
1 conflict
0xd742d13c…2b23
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0x758672cf6d…45c368
Audit this contract →
← previous block·next block →recent activity