← previous blocknext block →recent activity
Analyzing
Block #100,266,772
9 transactions · 9 stateful · 2026-08-29 19:24:49 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,266,772 · 9 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
1w05w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05adb823…6582
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x07d94be1…7fa8
0x34b655…2a6f
2 touches
0 conflicts
0x1a2055c7…9054
0x34b655…2a6f
2 touches
0 conflicts
0x1a2055c7…9055
0x34b655…2a6f
2 touches
0 conflicts
0x3cf5ed4a…c35d
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 0x05adb823c2…7d6582
Audit this contract →
← previous block·next block →recent activity