← previous blocknext block →recent activity
Analyzing
Block #105,581,665
19 transactions · 19 stateful · 2026-09-17 10:29:02 UTC
Parallelism
89/100
Blocked
21%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,581,665 · 19 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
1w03w04w15w06w18w012w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c0e49c9…7833
0x34b655…2a6f
4 touches
1 conflict
0xbdd0dc11…c952
0x23df56…3f97
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x040512ab…fe76
0x23df56…3f97
4 touches
1 conflict
0xac29e17e…11d8
0x23df56…3f97
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x945d1dbe…e1d7
0xc8689a…ee79
4 touches
1 conflict
0x2b7caca8…860f
0x34b655…2a6f
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 0x3c0e49c972…657833
Audit this contract →
← previous block·next block →recent activity