← previous blocknext block →recent activity
Analyzing
Block #100,605,314
28 transactions · 20 stateful · 2026-08-30 23:50:25 UTC
Parallelism
93/100
Blocked
15%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,605,314 · 28 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
12w014w015w116w018w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0xbf6c8372…cedc
0x065c9d…c394
3 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x52b2837f…4b7f
0x34b655…2a6f
2 touches
0 conflicts
0x65b1e075…7a54
0x34b655…2a6f
2 touches
0 conflicts
0x95a0b936…910b
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 0xe5bb3628b5…71e5e8
Audit this contract →
← previous block·next block →recent activity