← previous blocknext block →recent activity
Analyzing
Block #100,024,595
12 transactions · 12 stateful · 2026-08-28 23:04:11 UTC
Parallelism
50/100
Blocked
42%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,024,595 · 12 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w27w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2a76d80…ee44
0x34b655…2a6f
8 touches
6 conflicts
0x30b0b461…88ae
0x34b655…2a6f
6 touches
3 conflicts
0x1b19e074…20ba
0x34b655…2a6f
6 touches
3 conflicts
0xccdc1094…8a94
0x34b655…2a6f
4 touches
1 conflict
0x9a8482cc…8bee
0x34b655…2a6f
4 touches
1 conflict
0xf788c790…e66f
0x34b655…2a6f
4 touches
1 conflict
0xffaa25f5…1528
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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 0xd2a76d80a7…41ee44
Audit this contract →
← previous block·next block →recent activity