← previous blocknext block →recent activity
Analyzing
Block #107,443,464
20 transactions · 18 stateful · 2026-09-23 22:43:37 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,443,464 · 20 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
1w05w06w17w08w19w010w114w215w016w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8da4c229…0f5e
0x34b655…2a6f
4 touches
1 conflict
0xaf4b2c75…e60f
0x34b655…2a6f
4 touches
1 conflict
0xb066c72c…87d2
0x34b655…2a6f
4 touches
1 conflict
0x6286219a…0721
0x37db7f…ec7b
4 touches
1 conflict
0x8a35acfb…d1b0
0x37db7f…ec7b
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x8da4c229db…020f5e
Audit this contract →
← previous block·next block →recent activity