← previous blocknext block →recent activity
Analyzing
Block #100,628,659
29 transactions · 21 stateful · 2026-08-31 01:47:51 UTC
Parallelism
90/100
Blocked
43%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,628,659 · 29 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
1w02w03w16w08w014w115w216w018w119w120w021w122w125w226w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa9946775…e020
0xa6afd3…d132
4 touches
1 conflict
0x1dedc384…ff57
0x851145…3f07
4 touches
1 conflict
0x474e5df9…821f
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x88ecacda…04c9
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity