← previous blocknext block →recent activity
Analyzing
Block #107,817,384
24 transactions · 23 stateful · 2026-09-25 06:07:43 UTC
Parallelism
79/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,817,384 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w010w011w113w014w015w116w217w318w422w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0xc7679110…572d
0x34b655…2a6f
4 touches
1 conflict
0xa0a8c7a5…3422
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x7c7110ee…aebe
0x34b655…2a6f
4 touches
1 conflict
0xe4c6b0cb…0a26
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
6 conflicts on slot 0x42522e76ce…082592
Audit this contract →
← previous block·next block →recent activity