← previous blocknext block →recent activity
Analyzing
Block #100,614,624
25 transactions · 21 stateful · 2026-08-31 00:37:16 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,614,624 · 25 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
1w05w16w07w18w014w016w018w119w220w121w123w024w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c83a7b1…e305
0x34b655…2a6f
6 touches
3 conflicts
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x03d6a320…b69b
0x34b655…2a6f
4 touches
1 conflict
0x1e168c8b…6945
0x34b655…2a6f
4 touches
1 conflict
0x297de2d5…7396
0x34b655…2a6f
4 touches
1 conflict
0x3acf9416…7ddc
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0x9c83a7b19e…36e305
Audit this contract →
← previous block·next block →recent activity