← previous blocknext block →recent activity
Analyzing
Block #100,616,254
9 transactions · 6 stateful · 2026-08-31 00:45:27 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,616,254 · 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa140ac77…1f0c
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0004
0x2b46c0…1669
2 touches
0 conflicts
0xc12e10d9…77d5
0x2b46c0…1669
2 touches
0 conflicts
0x0203a60f…d0bd
0x34b655…2a6f
2 touches
0 conflicts
0x0476d77b…a514
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 0xa140ac77ab…ad1f0c
Audit this contract →
← previous block·next block →recent activity