← previous blocknext block →recent activity
Analyzing
Block #100,248,969
17 transactions · 17 stateful · 2026-08-29 17:54:34 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,248,969 · 17 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
2w03w05w06w113w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb22303…6db2
0x34b655…2a6f
4 touches
1 conflict
0xafb22303…6db3
0x34b655…2a6f
4 touches
1 conflict
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe1c07673…a4b4
0x34b655…2a6f
4 touches
1 conflict
0x21280422…0930
0x34b655…2a6f
4 touches
1 conflict
0x4de0b2a2…784f
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
1 conflict on slot 0xafb22303eb…7c6db2
Audit this contract →
← previous block·next block →recent activity