← previous blocknext block →recent activity
Analyzing
Block #107,450,980
22 transactions · 20 stateful · 2026-09-23 23:21:26 UTC
Parallelism
91/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,450,980 · 22 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
4w05w16w014w115w016w118w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9efd1cbe…bd9c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdced4209…6afa
0x34b655…2a6f
4 touches
1 conflict
0xe7e6031b…b25d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0311862a…7c5c
0x34b655…2a6f
4 touches
1 conflict
0x94618b89…2a23
0x754704…b603
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
1 conflict on slot 0x9efd1cbebb…a3bd9c
Audit this contract →
← previous block·next block →recent activity