← previous blocknext block →recent activity
Analyzing
Block #100,632,616
14 transactions · 14 stateful · 2026-08-31 02:07:46 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,632,616 · 14 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
3w04w15w06w18w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d5c5d72…914b
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x9ed5aa7d…9481
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xf8e6479f…f193
0x34b655…2a6f
4 touches
1 conflict
0x0431b6c8…4d5e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xfcdb5918…2b49
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
3 conflicts on slot 0x6d5c5d726f…33914b
Audit this contract →
← previous block·next block →recent activity