← previous blocknext block →recent activity
Analyzing
Block #100,705,810
18 transactions · 17 stateful · 2026-08-31 08:15:56 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,705,810 · 18 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
2w03w17w010w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9eaed5a0…9f17
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
2 touches
0 conflicts
0xcd26fba5…21c6
0x34b655…2a6f
2 touches
0 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
2 touches
0 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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 0x9eaed5a054…529f17
Audit this contract →
← previous block·next block →recent activity