← previous blocknext block →recent activity
Analyzing
Block #108,919,100
23 transactions · 19 stateful · 2026-09-29 02:36:30 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,919,100 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w19w010w112w214w117w118w219w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0xfd808de1…5c3c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0056
0x1b6862…e19c
4 touches
1 conflict
0x91ecc547…33f0
0x1b6862…e19c
4 touches
1 conflict
0xd0cf1adf…82b0
0x1b6862…e19c
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity