← previous blocknext block →recent activity
Analyzing
Block #100,439,066
14 transactions · 12 stateful · 2026-08-30 09:54:00 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,439,066 · 14 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
1w02w13w010w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fa6e1a0…c881
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xe2d50773…c39e
0x34b655…2a6f
4 touches
1 conflict
0x6d5d1fb5…86a7
0x34b655…2a6f
2 touches
0 conflicts
0xab3ad3dc…2a56
0x34b655…2a6f
2 touches
0 conflicts
0xba1edffb…323e
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 0x5fa6e1a013…9dc881
Audit this contract →
← previous block·next block →recent activity