← previous blocknext block →recent activity
Analyzing
Block #108,436,588
18 transactions · 18 stateful · 2026-09-27 10:04:04 UTC
Parallelism
89/100
Blocked
28%
Avg conflicts / tx
0.28
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,436,588 · 18 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
1w02w13w04w110w011w112w013w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xb58c5f09…1656
0x34b655…2a6f
4 touches
1 conflict
0x6c39a812…69d2
0x34b655…2a6f
4 touches
1 conflict
0xc2fe6ed6…f8be
0x34b655…2a6f
4 touches
1 conflict
0xc53f1beb…ac44
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: Perpl
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity