← previous blocknext block →recent activity
Analyzing
Block #100,614,674
33 transactions · 24 stateful · 2026-08-31 00:37:31 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,614,674 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w08w113w114w015w119w120w221w323w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd30ecce…02c0
0x34b655…2a6f
8 touches
6 conflicts
0x97e4c862…4419
0x34b655…2a6f
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0xb9b077a8…e029
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
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
6 conflicts on slot 0xfd30eccec1…4802c0
Audit this contract →
← previous block·next block →recent activity